sed s/KCP/kcp/g in the docs

On-behalf-of: @SAP [email protected]

Author: xrstf

cli/cmd/kubectl-kcp/cmd/kubectlKcp.go

@@ -37,17 +37,17 @@ import (
 func KubectlKcpCommand() *cobra.Command {
 	root := &cobra.Command{
 		Use:   "kcp",
-		Short: "kubectl plugin for KCP",
+		Short: "kubectl plugin for kcp",
 		Long: help.Doc(`
-			KCP is the easiest way to manage Kubernetes applications against one or
+			kcp is the easiest way to manage Kubernetes applications against one or
 			more clusters, by giving you a personal control plane that schedules your
 			workloads onto one or many clusters, and making it simple to pick up and
 			move. Advanced use cases including spreading your apps across clusters for
 			resiliency, scheduling batch workloads onto clusters with free capacity,
 			and enabling collaboration for individual teams without having access to
 			the underlying clusters.
 
-			This command provides KCP specific sub-command for kubectl.
+			This command provides kcp-specific sub-command for kubectl.
 		`),
 		SilenceUsage:  true,
 		SilenceErrors: true,

docs/content/concepts/authentication/index.md

@@ -13,7 +13,7 @@ For detailed instructions on running kcp with a specific authentication strategy
 
 - [OIDC]
 
-## KCP Front Proxy Authentication
+## kcp Front Proxy Authentication
 
 kcp-front-proxy is a reverse proxy that accepts client certificates and forwards Common Name (as username) and Organizations (as groups) to the backend API servers in HTTP headers. The proxy terminates TLS and communicates with API servers via mTLS. Traffic is routed based on paths.
 
@@ -50,30 +50,30 @@ These can be passed by setting `--authentication-pass-on-groups` and `--authenti
 By default, kcp-front-proxy is configured to drop `system:masters` and `system:kcp:logical-cluster-admin`.
 This ensures that highly privileged users do not receive elevated access when passing through the proxy.
 
-## KCP Server Admin Authentication
+## kcp Server Admin Authentication
 
 Admin Authenticator sets up user roles and groups and generates authentication tokens and `admin.kubeconfig` file. The authentication process relies on Kubernetes authenticated group authenticator.
 To enable admin authentication in the kcp server, you need run it in the development mode with the `--batteries-included=admin` flag set.
 This setting is currently enabled by default when running the `kcp` binary, but is disabled in the Helm chart.
 
 ### Users and Groups
 
-| **User Name**   | **Role**                                                                                                                           | **Groups**                           |
-|-----------------|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|
-| **shard-admin** | Member of the privileged system group. This user bypasses most kcp authorization checks.                                           | system:masters|
-| **kcp-admin**   | Member of the system:kcp:admin group. This user is subject to kcp authorization checks. | system:kcp:admin           |
-| **user**        | Regular non-admin user who is not a part of any predefined groups.                                                                 | None                                 |
+| **User Name**   | **Role**                                                                                 | **Groups**        |
+|-----------------|------------------------------------------------------------------------------------------|-------------------|
+| **shard-admin** | Member of the privileged system group. This user bypasses most kcp authorization checks. | system:masters    |
+| **kcp-admin**   | Member of the system:kcp:admin group. This user is subject to kcp authorization checks.  | system:kcp:admin  |
+| **user**        | Regular non-admin user who is not a part of any predefined groups.                       | None              |
 
 ### Generated Kubeconfig Contexts
 
 kcp server generates a kubeconfig file (admin.kubeconfig) containing credentials for the predefined users. This file allows users to authenticate into different logical clusters.
 
-| **Context Name** | **Cluster Endpoint** |
-|------------------|----------------------|
-| **root**         | /clusters/root       |
-| **base**         | /clusters/base       |
+| **Context Name** | **Cluster Endpoint**   |
+|------------------|------------------------|
+| **root**         | /clusters/root         |
+| **base**         | /clusters/base         |
 | **system:admin** | /clusters/system:admin |
-| **shard-base**   | /clusters/base       |
+| **shard-base**   | /clusters/base         |
 
 ## Pages
 

docs/content/concepts/authorization/index.md

@@ -5,7 +5,7 @@ description: >
 
 # Authorization
 
-Within workspaces, KCP implements the same RBAC-based authorization mechanism as Kubernetes.
+Within workspaces, kcp implements the same RBAC-based authorization mechanism as Kubernetes.
 Other authorization schemes (i.e. ABAC) are not supported.
 Generally, the same (cluster) role and (cluster) role binding principles apply exactly as in Kubernetes.