Fix kcp casing once and for all by xrstf · Pull Request #3665 · kcp-dev/kcp

xrstf · 2025-10-20T15:16:47Z

Summary

It irks me that it's sometimes kcp, sometimes KCP and in extreme cases even Kcp. For no technical reason other than consistency, I vote that we enshrine the correct spelling (all lowercase) in the FAQ and adjust all files accordingly.

This PR also fixes the rebasing docs a bit and adds a note that they are probably severely outdated since we moved to monorepo. The sample screenshot of GitHub is now included as well and shrunk by optipng by nearly 50% :)

I did not touch the boilerplate header as I am not sure about the CNCF rammifications, but I would personally of course also change them. If we can.

What Type of PR Is This?

/kind cleanup

Release Notes

NONE

kcp-ci-bot · 2025-10-20T15:25:23Z

LGTM label has been added.

Details

Git tree hash: d9923af3dfee347737df83329aef52217b7d40d5

kcp-ci-bot · 2025-10-20T15:26:19Z

New changes are detected. LGTM label has been removed.

xrstf · 2025-10-20T17:27:03Z

/retest

embik · 2025-10-21T06:54:43Z

FAQ.md


+## What does kcp stand for / how to spell it?
+
+`kcp` stands for "Kube for Control Plane" and should always be written in lowercase letters.


Afaik our official position is that it doesn't stand for anything.

I thought so too, but then I found https://github.com/kcp-dev/kcp/blob/main/cmd/kcp/kcp.go#L51.

I also remember someone telling me that kcp effectively stands for nothing and CERTAINLY NOT "Kubernetes control plane", but since then I heard many folks use the "kube for control plane" mantra.

No real opinion on my side.

I would vote for kcp - Kubernetes-like Control Planes. This was clicked in my head for a long time.
I leave the final vote for @sttts :)

+1 for @mjudeikis's proposal.

"K-ControlPlane"

I can agree with MJ's earlier proposal ("kcp - Kubernetes-like Control Planes") if CNCF allows it.

Can we check with cncf?

I checked with CNCF folks and the inofficial statement through the grapevines was:

[this decision] should not need CNCF approval

[kcp devs] must just make sure to follow kcp governance

@xmudrii Is the decision here done, did all maintainers vote?

mjudeikis

just close the one pending and merge

mjudeikis · 2025-10-24T06:53:18Z

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

+		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


can we remove this Kubernetes applications against. Applications are confusing.

ALl thi section is somehow wrong.

I replaced it with the current short intro we have in our Readme/docs.

Can we replace the doc here with this? https://github.com/xrstf/kcp/blob/47233a3c7b3f7fcb1c0e2ed9f9c8a04801bc9cf9/cmd/kcp/kcp.go#L53-L63

mjudeikis · 2025-10-24T06:55:30Z

FAQ.md


+## What does kcp stand for / how to spell it?
+
+`kcp` stands for "Kube for Control Plane" and should always be written in lowercase letters.


I would vote for kcp - Kubernetes-like Control Planes. This was clicked in my head for a long time.
I leave the final vote for @sttts :)

On-behalf-of: @SAP christoph.mewes@sap.com

kcp-ci-bot · 2025-11-04T14:47:02Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from embik. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS
config/crds/OWNERS
pkg/admission/OWNERS
staging/src/github.com/kcp-dev/sdk/apis/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

kcp-ci-bot · 2025-11-04T15:26:12Z

@xrstf: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kcp-build-image	`47233a3`	link	true	`/test pull-kcp-build-image`
pull-kcp-test-unit	`47233a3`	link	true	`/test pull-kcp-test-unit`
pull-kcp-lint	`47233a3`	link	true	`/test pull-kcp-lint`
pull-kcp-test-e2e-shared	`47233a3`	link	true	`/test pull-kcp-test-e2e-shared`
pull-kcp-test-e2e-sharded	`47233a3`	link	true	`/test pull-kcp-test-e2e-sharded`

Full PR test history

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

kcp-ci-bot · 2025-11-05T06:42:29Z

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

ntnn · 2026-02-10T22:35:31Z

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

+		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


Can we replace the doc here with this? https://github.com/xrstf/kcp/blob/47233a3c7b3f7fcb1c0e2ed9f9c8a04801bc9cf9/cmd/kcp/kcp.go#L53-L63

ntnn · 2026-02-10T22:38:38Z

docs/content/concepts/workspaces/workspace-types.md

 leader election is enabled). It is accessible via `/clusters/system:admin`.

-# Workspace Type Extensions and Constraints
+## Workspace Type Extensions and Constraints


Was this deliberate? I feel like workspace types being their own "section" would make sense.

ntnn · 2026-02-10T22:39:46Z

docs/content/contributing/guides/rebasing-kubernetes/index.md

 9. Open a PR; get it reviewed and merged.

-# 3. Update kcp-dev/client-go
+## 3. Update kcp-dev/client-go


I think we can scrap the changes for rebasing-kubernetes in favour of the doc update PR and fix casing there as well? Just so it doesn't cause a merge conflict. Up to you though.

ntnn · 2026-02-10T22:43:11Z

FAQ.md


+## What does kcp stand for / how to spell it?
+
+`kcp` stands for "Kube for Control Plane" and should always be written in lowercase letters.


@xmudrii Is the decision here done, did all maintainers vote?

xmudrii · 2026-02-11T10:05:17Z

@ntnn The vote is still ongoing, I'll try pinging some folks directly by the end of the week.

olamilekan000 approved these changes Oct 20, 2025

View reviewed changes

kcp-ci-bot assigned olamilekan000 Oct 20, 2025

kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Oct 20, 2025

kcp-ci-bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 20, 2025

kcp-ci-bot requested a review from olamilekan000 October 20, 2025 15:26

embik requested changes Oct 21, 2025

View reviewed changes

kcp-ci-bot assigned embik Oct 21, 2025

mjudeikis reviewed Oct 24, 2025

View reviewed changes

xrstf force-pushed the lowercase-kcp branch from d7d06c8 to c948238 Compare October 27, 2025 15:36

kcp-ci-bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 27, 2025

xrstf force-pushed the lowercase-kcp branch from c948238 to 81ed0a7 Compare October 28, 2025 14:01

kcp-ci-bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Oct 28, 2025

xrstf added 5 commits November 4, 2025 15:46

sed s/KCP/kcp/g in the docs

e0a94a4

On-behalf-of: @SAP christoph.mewes@sap.com

consistently lowercase 'kcp' everywhere

7d6d919

On-behalf-of: @SAP christoph.mewes@sap.com

codegen

c7b2cc5

On-behalf-of: @SAP christoph.mewes@sap.com

fix more uppercased kcp's

d33c1e1

On-behalf-of: @SAP christoph.mewes@sap.com

update kcp CLI help text

47233a3

On-behalf-of: @SAP christoph.mewes@sap.com

xrstf force-pushed the lowercase-kcp branch from 81ed0a7 to 47233a3 Compare November 4, 2025 14:46

kcp-ci-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 4, 2025

kcp-ci-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 5, 2025

xrstf mentioned this pull request Nov 17, 2025

Provision RBAC for Kubeconfigs inside kcp kcp-dev/kcp-operator#91

Merged

ntnn reviewed Feb 10, 2026

View reviewed changes


		## What does kcp stand for / how to spell it?

		`kcp` stands for "Kube for Control Plane" and should always be written in lowercase letters.

Comments

Conversation

xrstf commented Oct 20, 2025

Summary

What Type of PR Is This?

Release Notes

Uh oh!

kcp-ci-bot commented Oct 20, 2025

Uh oh!

kcp-ci-bot commented Oct 20, 2025

Uh oh!

xrstf commented Oct 20, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mjudeikis left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kcp-ci-bot commented Nov 4, 2025

Uh oh!

kcp-ci-bot commented Nov 4, 2025

Uh oh!

kcp-ci-bot commented Nov 5, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

xmudrii commented Feb 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants