Skip to content

Commit

Permalink
docs: broken URL
Browse files Browse the repository at this point in the history
  • Loading branch information
karl-cardenas-coding committed Oct 22, 2023
1 parent c4bce6e commit 959712b
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 3 deletions.
3 changes: 1 addition & 2 deletions docs/api-content/api-docs/1-introduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,8 +29,7 @@ Palette supports two types of user authentication methods:
Palette uses API keys to provide secure API authentication and authorization. This enables the usage of Palette APIs without requiring user credentials such as username and password. The API key must be present in individual API requests in order to authenticate and authorize the request. The API Key is passed as part of the HTTP request header and in the following format:
* Key: ApiKey
* Value: API key copied from the Palette Console. E.g. QMOI1ZVKVIoW6LM6uXqSWFPsjmt0juvl

[Read More...](/user-management/user-authentication)

## Requests

All requests are in the `JSON` format. In general, the request payload has three sections: *metadata, spec and status*.
Expand Down
2 changes: 1 addition & 1 deletion docs/docs-content/release-notes.md
Original file line number Diff line number Diff line change
Expand Up @@ -1288,7 +1288,7 @@ Spectro Cloud Palette 2.5.0 was released with support for Tencent Kubernetes Eng
Palette 2.3.0 includes the following enhancements:

- Added support for cluster-centric detailed [**Namespace Management** and granular **RBAC**](/clusters/cluster-management/cluster-rbac). Previously this capability was only available via workspaces.
- Enabled secure and straightforward user authentication with [**API Keys**](/user-management/user-authentication) to access the APIs without referring to user credentials.
- Enabled secure and straightforward user authentication with **API Keys** to access the APIs without referring to user credentials.
- Tenant administrators can now get an [**aggregated view**](/clusters/#scope) of clusters across all the projects under their tenant.
- Added support for [**Taints**](/clusters/cluster-management/taints/#overviewontaints) that can be applied to a node pool to restrict a set of intolerant pods getting scheduled to an inadequate node.
- Added support for [**Labels**](/clusters/cluster-management/taints/#overviewonlabels) to constrain pods so that they can run on a particular set of nodes.
Expand Down

0 comments on commit 959712b

Please sign in to comment.