PoC Using helm for kuadrant deployment #1
Conversation
This file contains 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
5 tasks
|
Another downside to using dummy CRDs is that we might not be able to easily spot absence of CRDs from the OLM bundle. |
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.
I managed to force helm (using a small cheat) to create CRs of unknown type by providing dummy CRD (kuadrant).
Kuadrant objects gets created with all spec fields, OLM then tries to install "proper" CRD . This mechanism enables having operator and operands installation in a single chart. However Kuadrant object is not checked against any OpenAPI specification during its creation and the only mechanism that prevents mistakes in object's definition is refusal of application of new CRD via InstallPlan.