Fix kcp casing once and for all

.goreleaser.yaml

@@ -120,8 +120,8 @@ krews:
     token: "{{ .Env.KREW_GITHUB_TOKEN }}"
   homepage: "https://kcp.io/"
   description: |
-    KCP cli plugin for kubectl. Enables you to work with KCP.
-  short_description: "KCP cli plugin for kubectl."
+    kcp cli plugin for kubectl. Enables you to work with kcp.
+  short_description: "kcp cli plugin for kubectl."
   skip_upload: auto
 - name: ws
   ids:
@@ -132,8 +132,8 @@ krews:
     token: "{{ .Env.KREW_GITHUB_TOKEN }}"
   homepage: "https://kcp.io/"
   description: |
-    KCP workspace cli plugin for kubectl. Enables you to manage your KCP workspaces.
-  short_description: "KCP workspace cli plugin for kubectl."
+    kcp workspace cli plugin for kubectl. Enables you to manage your kcp workspaces.
+  short_description: "kcp workspace cli plugin for kubectl."
   skip_upload: auto
 - name: create-workspace
   ids:
@@ -144,6 +144,6 @@ krews:
     token: "{{ .Env.KREW_GITHUB_TOKEN }}"
   homepage: "https://kcp.io/"
   description: |
-    KCP create workspace cli plugin for kubectl. Enables you to create KCP workspaces.
-  short_description: "KCP create workspace cli plugin for kubectl."
+    kcp create workspace cli plugin for kubectl. Enables you to create kcp workspaces.
+  short_description: "kcp create workspace cli plugin for kubectl."
   skip_upload: auto

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/cmd/kubectl-kcp/cmd/kubectlKcp.go

@@ -38,17 +38,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,

cli/pkg/workspace/cmd/cmd.go

@@ -89,14 +89,14 @@ 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>] [-i|--interactive]",
-		Short:            "Manages KCP workspaces",
+		Short:            "Manages kcp workspaces",
 		Example:          fmt.Sprintf(workspaceExample, cliName),
 		SilenceUsage:     true,
 		TraverseChildren: true,
 		RunE: func(cmd *cobra.Command, args []string) error {
 			if interactive {
 				if len(args) != 0 {
-					return fmt.Errorf("interactive mode does not accept arguments")
+					return errors.New("interactive mode does not accept arguments")
 				}
 				treeOpts.Interactive = true
 				if err := treeOpts.Validate(); err != nil {

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,18 +48,22 @@ 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
-			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
-			clusters for resiliency, scheduling batch workloads onto clusters with
-			free capacity, and enabling collaboration for individual teams without
-			having access to the underlying clusters.
-
-			To get started, launch a new cluster with 'kcp start', which will
-			initialize your personal control plane and write an admin kubeconfig file
+			kcp is a Kubernetes-like control plane focusing on
+
+			* being a control plane for many independent, isolated "clusters"
+			  known as workspaces,
+			* enabling API service providers to offer APIs centrally
+			  using multi-tenant operators and
+			* easy API consumption for users in their workspaces.
+
+			kcp can be a building block for SaaS service providers who need a
+			massively multi-tenant platform to offer services to a large number of
+			fully isolated tenants using Kubernetes-native APIs.
+
+			To get started, launch a new instance with 'kcp start', which will
+			initialize your personal shard and write an admin kubeconfig file
 			to disk.
 		`),
 		SilenceUsage:  true,

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",
 	}
 )

cmd/kcp/options/generic.go

@@ -38,7 +38,7 @@ func NewGeneric(rootDir string) *GenericOptions {
 }
 
 func (o *GenericOptions) AddFlags(fss *cliflag.NamedFlagSets) {
-	fs := fss.FlagSet("KCP")
+	fs := fss.FlagSet("kcp")
 	fs.StringVar(&o.RootDirectory, "root-directory", o.RootDirectory, "Root directory. Set to \"\" to disable file (e.g. certificates) generation in a root directory.")
 	fs.StringVar(&o.MappingFile, "miniproxy-mapping-file", o.MappingFile, "DEVELOPMENT ONLY. Path to additional mapping file to be used by mini-front-proxy. This should not be used in production. For production usecase use front-proxy component instead.")
 }
@@ -75,7 +75,7 @@ func (o *GenericOptions) Validate() []error {
 	return nil
 }
 
-// mkdirRoot creates the root configuration directory for the KCP
+// mkdirRoot creates the root configuration directory for the kcp
 // server. This has to be done early before we start bringing up server
 // components to ensure that we set the initial permissions correctly,
 // since otherwise components will create it as a side-effect.

cmd/virtual-workspaces/options/options.go

@@ -98,7 +98,7 @@ func (o *Options) AddFlags(flags *pflag.FlagSet) {
 	flags.StringVar(&o.ShardExternalURL, "shard-external-url", o.ShardExternalURL, "URL used by outside clients to talk to the kcp shard this virtual workspace is related to")
 
 	flags.StringVar(&o.KubeconfigFile, "kubeconfig", o.KubeconfigFile,
-		"The kubeconfig file of the KCP instance that hosts workspaces.")
+		"The kubeconfig file of the kcp instance that hosts workspaces.")
 	_ = cobra.MarkFlagRequired(flags, "kubeconfig")
 
 	flags.StringVar(&o.Context, "context", o.Context, "Name of the context in the kubeconfig file to use")

config/crds/apis.kcp.io_apibindings.yaml

@@ -79,7 +79,7 @@ spec:
                         This is the identity for a given APIExport that the APIResourceSchema belongs to.
                         The hash can be found on APIExport and APIResourceSchema's status.
                         It will be empty for core types.
-                        Note that one must look this up for a particular KCP instance.
+                        Note that one must look this up for a particular kcp instance.
                       type: string
                     resource:
                       description: |-
@@ -193,7 +193,7 @@ spec:
                         This is the identity for a given APIExport that the APIResourceSchema belongs to.
                         The hash can be found on APIExport and APIResourceSchema's status.
                         It will be empty for core types.
-                        Note that one must look this up for a particular KCP instance.
+                        Note that one must look this up for a particular kcp instance.
                       type: string
                     resource:
                       description: |-
@@ -373,7 +373,7 @@ spec:
                         This is the identity for a given APIExport that the APIResourceSchema belongs to.
                         The hash can be found on APIExport and APIResourceSchema's status.
                         It will be empty for core types.
-                        Note that one must look this up for a particular KCP instance.
+                        Note that one must look this up for a particular kcp instance.
                       type: string
                     resource:
                       description: |-
@@ -493,7 +493,7 @@ spec:
                         This is the identity for a given APIExport that the APIResourceSchema belongs to.
                         The hash can be found on APIExport and APIResourceSchema's status.
                         It will be empty for core types.
-                        Note that one must look this up for a particular KCP instance.
+                        Note that one must look this up for a particular kcp instance.
                       type: string
                     resource:
                       description: |-
@@ -643,7 +643,7 @@ spec:
                         This is the identity for a given APIExport that the APIResourceSchema belongs to.
                         The hash can be found on APIExport and APIResourceSchema's status.
                         It will be empty for core types.
-                        Note that one must look this up for a particular KCP instance.
+                        Note that one must look this up for a particular kcp instance.
                       type: string
                     resource:
                       description: |-
@@ -863,7 +863,7 @@ spec:
                         This is the identity for a given APIExport that the APIResourceSchema belongs to.
                         The hash can be found on APIExport and APIResourceSchema's status.
                         It will be empty for core types.
-                        Note that one must look this up for a particular KCP instance.
+                        Note that one must look this up for a particular kcp instance.
                       type: string
                     resource:
                       description: |-

config/crds/apis.kcp.io_apiexports.yaml

@@ -166,7 +166,7 @@ spec:
                         This is the identity for a given APIExport that the APIResourceSchema belongs to.
                         The hash can be found on APIExport and APIResourceSchema's status.
                         It will be empty for core types.
-                        Note that one must look this up for a particular KCP instance.
+                        Note that one must look this up for a particular kcp instance.
                       type: string
                     resource:
                       description: |-
@@ -409,7 +409,7 @@ spec:
                         This is the identity for a given APIExport that the APIResourceSchema belongs to.
                         The hash can be found on APIExport and APIResourceSchema's status.
                         It will be empty for core types.
-                        Note that one must look this up for a particular KCP instance.
+                        Note that one must look this up for a particular kcp instance.
                       type: string
                     resource:
                       description: |-

config/crds/core.kcp.io_shards.yaml

@@ -60,7 +60,7 @@ spec:
             properties:
               baseURL:
                 description: |-
-                  baseURL is the address of the KCP shard for direct connections, e.g. by some
+                  baseURL is the address of the kcp shard for direct connections, e.g. by some
                   front-proxy doing the fan-out to the shards.
                 format: uri
                 minLength: 1

config/root-phase0/apiexport-shards.core.kcp.io.yaml

@@ -7,7 +7,7 @@ spec:
   resources:
   - group: core.kcp.io
     name: shards
-    schema: v240903-d6797056a.shards.core.kcp.io
+    schema: v251020-aa1b96e5d.shards.core.kcp.io
     storage:
       crd: {}
 status: {}

config/root-phase0/apiresourceschema-shards.core.kcp.io.yaml

@@ -2,7 +2,7 @@ apiVersion: apis.kcp.io/v1alpha1
 kind: APIResourceSchema
 metadata:
   creationTimestamp: null
-  name: v240903-d6797056a.shards.core.kcp.io
+  name: v251020-aa1b96e5d.shards.core.kcp.io
 spec:
   group: core.kcp.io
   names:
@@ -57,7 +57,7 @@ spec:
           properties:
             baseURL:
               description: |-
-                baseURL is the address of the KCP shard for direct connections, e.g. by some
+                baseURL is the address of the kcp shard for direct connections, e.g. by some
                 front-proxy doing the fan-out to the shards.
               format: uri
               minLength: 1

contrib/kcp-dex/README.md

@@ -1,4 +1,4 @@
-# KCP Dex
+# kcp Dex
 
 How to run local kcp with dex.
 
@@ -23,7 +23,7 @@ GOBIN=$(pwd)/bin go install github.com/mjudeikis/genkey
 * Run dex: `./bin/dex serve ../contrib/kcp-dex/kcp-config.yaml `
 
 
-### KCP
+### kcp
 
 Start kcp with oidc enabled, you can either use the OIDC flags or structured authentication configuration from a file. Example configuration is shown in `auth-config.yaml`.
 

contrib/kcp-dex/kcp-config.yaml

@@ -13,7 +13,7 @@ staticClients:
     public: true
     redirectURIs:
     - http://localhost:8000
-    name: 'KCP App'
+    name: 'kcp App'
     secret: Z2Fyc2lha2FsYmlzdmFuZGVuekWplCg==
 
 # Let dex keep a list of passwords which can be used to login to dex.