Conversation
Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
SAY-5
requested review from
Ronkahn21,
danbar2,
gflarity,
sanjaychatterjee,
shayasoolin and
unmarshall
as code owners
September 2, 2026 21:10
Contributor
Author
|
Closing, #812 landed the same ct to ctb change and shipped in alpha.13. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
/kind api
What this PR does / why we need it:
ClusterTopologyBinding still claims the shortName ct, which was ClusterTopology's shortName before the rename in #616. Helm does not remove the old CRD on upgrade, so a cluster that ran the pre-rename version ends up with both CRDs claiming ct, the new CRD never reaches Established, and the operator crash loops on startup. Giving the renamed type its own shortName ctb removes the collision.
Which issue(s) this PR fixes:
Fixes #801
Special notes for your reviewer:
Ran make --directory=operator/api generate to regenerate the CRD yaml instead of hand editing it.
Does this PR introduce a API change?
Additional documentation e.g., enhancement proposals, usage docs, etc.: