From 959712b8b66f24385054a27409a0c84df7b7c62e Mon Sep 17 00:00:00 2001 From: Karl Cardenas Date: Sun, 22 Oct 2023 04:49:36 -0700 Subject: [PATCH] docs: broken URL --- docs/api-content/api-docs/1-introduction.md | 3 +-- docs/docs-content/release-notes.md | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/api-content/api-docs/1-introduction.md b/docs/api-content/api-docs/1-introduction.md index e30515f6ec..51762f858c 100644 --- a/docs/api-content/api-docs/1-introduction.md +++ b/docs/api-content/api-docs/1-introduction.md @@ -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*. diff --git a/docs/docs-content/release-notes.md b/docs/docs-content/release-notes.md index f7977c45d9..cc6419ca83 100644 --- a/docs/docs-content/release-notes.md +++ b/docs/docs-content/release-notes.md @@ -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.