Dev Override for Kustomize (PROJQUAY-992) #314
Merged
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.
Issue: https://issues.redhat.com/browse/PROJQUAY-992
Changelog: Allow overriding Kustomize using a defined
ConfigMap
.Docs: N/a
Testing:
ConfigMap
calledquay-dev-kustomize
with the following contents in thekustomization.yaml
key:CatalogSource
.QuayRegistry
withspec.desiredVersion
set todev
.Operator should deploy Quay app container using the image override.
Details: By using Kustomize and having the static k8s files present in the Operator container, we lend ourselves to an escape hatch for overriding the deployed container images and other aspects of the
QuayRegistry
. This is done at the Operator level, so everyQuayRegistry
will be deployed using these overrides. Therefore this is for dev/debugging purposes and should not be used in production.