rename v2 MCP resource #109
Merged
+40
−40
Conversation
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
ValentinGerlach
approved these changes
Aug 13, 2025
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 this PR does / why we need it:
If we use the same resource name and group and just a different version, k8s will try to convert between both versions. We do not want that, since we want to use the old and the new version in parallel for some time for an easier migration.
Therefore, we had to rename the new MCP version. I just renamed it to
ManagedControlPlaneV2, it will likely get a new name in the near future when we adapt our naming schema.Which issue(s) this PR fixes:
Related to openmcp-project/backlog#210
Special notes for your reviewer:
Release note: