Add the new child CRs for controller #60
Closed
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
…we will need to address at some point
…sense. Also expanded the amount of configuration options available by using podSpec
…es-operator-api-v1alpha1-design.md
Member
Author
|
I just realised that deleting the existing API specs would cause too many build issues at once. I'm closing this, and will create a separate PR with only additional CRs, and rebased branch. |
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.
This does not introduce MultigresCluster and top level definitions, as they are still being discussed which shape to take.
The child CRs should help create controller logic based on them.
This is branched off from #54, and will require an extra PR to manage MultigresCluster setup, as well as any other top level definitions.