consistently lowercase 'kcp' everywhere

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

Author: xrstf

ADOPTERS.md

@@ -8,4 +8,4 @@ Listed below are organizations that have adopted kcp in one way or another. We a
 | Kubermatic    | Kubermatic is building Kubermatic Developer Platform (KDP), an internal developer platform (IdP) product that uses kcp as its global API control plane.  | Development | [Product Website](https://www.kubermatic.com/products/kubermatic-developer-platform/) |
 | Faros.sh      | Faros is building a control-plane-as-a-service to access & manage multiple Kubernetes clusters across public and private deployments. | Development | - |
 | SAP           | SAP is developing an open reference architecture (ApeiroRA) with a Platform Mesh that leverages kcp as its foundation, enabling service providers to seamlessly connect and interact through unified KRM-based APIs in a cloud-edge continuum. | Development | [Website](https://apeirora.eu/) |
-| Upbound       | We use KCP within our Cloud Managed Control Planes product to provide multi-tenant access to the underlying hostcluster. | Production | - |
+| Upbound       | We use kcp within our Cloud Managed Control Planes product to provide multi-tenant access to the underlying hostcluster. | Production | - |

CONTRIBUTING.md

@@ -4,9 +4,9 @@ We're thrilled that you're interested in contributing to kcp! Please visit our
 [full contributing guide](https://docs.kcp.io/kcp/main/contributing) on our documentation site.
 
 Beside that, what coverns the project and all contributions to it must follow
-the [KCP Project Governance](./GOVERNANCE.md).
+the [kcp Project Governance](./GOVERNANCE.md).
 
-From the KCP Project Governance, the following manifesto should guide the technical
+From the kcp Project Governance, the following manifesto should guide the technical
 decisions through-out all contributions:
 
 > kcp maintainers strive to be good citizens in the Kubernetes project.

FAQ.md

@@ -8,12 +8,11 @@ kcp is a highly-multi-tenant Kubernetes control-plane, built for SaaS service-pr
 
 Check out our [concepts](https://github.com/kcp-dev/kcp/blob/main/docs/concepts.md) document and feel free to open an issue if something is not covered.
 
-
 ## If kcp is a Kubernetes API server without pod-like APIs, how do resources like Deployments get scheduled?
 
 kcp has a concept called [syncer](https://github.com/kcp-dev/kcp/blob/main/docs/concepts.md#syncer) which is installed on each [SyncTarget](https://github.com/kcp-dev/kcp/blob/main/docs/concepts.md#workload-cluster). The [syncer](https://github.com/kcp-dev/kcp/blob/main/docs/concepts.md#syncer) negotiates, with kcp, a set of APIs to make accessible in the workspace. This may include things like [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) or other resources you may explicitly configure the syncer to synchronize to kcp. Once these APIs are made available in your [Workspace](https://github.com/kcp-dev/kcp/blob/main/docs/concepts.md#workspace) you may then create resources of that type. From there, the [Location and Placement](https://github.com/kcp-dev/kcp/blob/main/docs/concepts.md#location) APIs help determine which [Location](https://github.com/kcp-dev/kcp/blob/main/docs/concepts.md#location) your deployable resource lands on.
 
-## Will KCP be able to pass the K8S conformance tests in [CNCF Conformance Suites](https://www.cncf.io/certification/software-conformance/)?
+## Will kcp be able to pass the K8S conformance tests in [CNCF Conformance Suites](https://www.cncf.io/certification/software-conformance/)?
 
 No, the Kubernetes conformance suites require that all Kubernetes APIs are supported and kcp does not support all APIs out of the box (for instance, Pods).
 
@@ -69,3 +68,6 @@ Shards in kcp represent a single apiserver and etcd/db instance.  This is how kc
 
 You're in the right place. Clone this repo and run `make install WHAT=./cli/cmd/kubectl-kcp`.
 
+## What does kcp stand for / how to spell it?
+
+`kcp` stands for "Kube for Control Plane" and should always be written in lowercase letters.

GOVERNANCE.md

@@ -1,4 +1,4 @@
-# KCP Project Governance
+# kcp Project Governance
 
 The kcp project is dedicated to democratizing Control Planes beyond container
 orchestration. This governance explains how the project is run.
@@ -177,7 +177,7 @@ mailing list and put on hold until the necessary majority has been reached.
 
 Any Maintainer may submit a [vote](#voting) to create a new subproject under the
 kcp-dev GitHub organization. Subprojects are governed by all Maintainers, but may
-take on additional Subproject Maintainers that are only responsible for the 
+take on additional Subproject Maintainers that are only responsible for the
 specific subproject.
 
 It is the combined responsibility of Maintainers and Subproject Maintainers

cli/pkg/workspace/cmd/cmd.go

@@ -83,7 +83,7 @@ func New(streams genericclioptions.IOStreams) (*cobra.Command, error) {
 	cmd := &cobra.Command{
 		Aliases:          []string{"ws", "workspaces"},
 		Use:              "workspace [create|create-context|use|current|<workspace>|..|.|-|~|<root:absolute:workspace>]",
-		Short:            "Manages KCP workspaces",
+		Short:            "Manages kcp workspaces",
 		Example:          fmt.Sprintf(workspaceExample, cliName),
 		SilenceUsage:     true,
 		TraverseChildren: true,

cli/pkg/workspace/plugin/scheme.go

@@ -24,7 +24,7 @@ import (
 
 func init() {
 	// The metav1.TableXXX types (that are in the metav1 scheme) are not added by default
-	// to the generated KCP clientset scheme.
+	// to the generated kcp clientset scheme.
 	// So when we want to get the result of a request done with this clientset as a table,
 	// it doesn't know the Table types and returns an error.
 	//

cmd/cache-server/main.go

@@ -51,7 +51,7 @@ func main() {
 	serverOptions := options.NewOptions(*rootDir)
 	cmd := &cobra.Command{
 		Use:   "cache-server",
-		Short: "Runs the cache server for KCP",
+		Short: "Runs the cache server for kcp",
 		Long: help.Doc(`
             Starts a server that hosts data/resources that are required by shards.
             It serves as a cache helping to reduce the storage that would have to

cmd/kcp-front-proxy/options/options.go

@@ -48,7 +48,7 @@ func (o *Options) AddFlags(fss *cliflag.NamedFlagSets) {
 	logsapiv1.AddFlags(o.Logs, fss.FlagSet("logging"))
 
 	// add flags that are filtered out from upstream, but overridden here with our own version
-	fss.FlagSet("KCP").Var(kcpfeatures.NewFlagValue(), "feature-gates", ""+
+	fss.FlagSet("kcp").Var(kcpfeatures.NewFlagValue(), "feature-gates", ""+
 		"A set of key=value pairs that describe feature gates for alpha/experimental features. "+
 		"Options are:\n"+strings.Join(kcpfeatures.KnownFeatures(), "\n")) // hide kube-only gates
 }

cmd/kcp/kcp.go

@@ -48,9 +48,9 @@ import (
 func main() {
 	cmd := &cobra.Command{
 		Use:   "kcp",
-		Short: "Kube for Control Plane (KCP)",
+		Short: "Kube for Control Plane (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. It supports advanced use cases such as spreading your apps across

cmd/kcp/options/flags.go

@@ -29,12 +29,12 @@ var (
 		"misc",
 		"secure serving",
 		"traces",
-		"KCP Authentication",
-		"KCP Authorization",
-		"KCP Virtual Workspaces",
-		"KCP Controllers",
-		"KCP Home Workspaces",
-		"KCP Cache Server",
-		"KCP",
+		"kcp Authentication",
+		"kcp Authorization",
+		"kcp Virtual Workspaces",
+		"kcp Controllers",
+		"kcp Home Workspaces",
+		"kcp Cache Server",
+		"kcp",
 	}
 )