Fix DataPlane/BuildPlane CRD docs to use clusterAgent instead of agent #237
+50
−45
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
yashodgayashan
approved these changes
Jan 20, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
fixes field mismatch from openchoreo/openchoreo#1501
docs were still showing
spec.agent.enabledandkubernetesClusterfields but the API changed tospec.clusterAgentin openchoreo/openchoreo#1294. users following the multi-cluster guide would get invalid CRD errors.changes:
spec.agent→spec.clusterAgent, removedenabledfieldkubernetesClusterwithclusterAgentfor DataPlane and BuildPlane schemasplaneID, gateway ports,imagePullSecretRefs,secretStoreRefrelates to openchoreo/openchoreo#1294