Add image.registry field #489
Open
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 change adds the
image.registryvalue to the helm-chart, and changes the Atlantis StatefulSet to use this new value when composing the Atlantis image name to pull.This change is backwards compatible. No breaking change since the registry value defaults to ghcr.io/
why
In cases where you have a multi-region/multi-environment deployment and use container image caches, you want to be able to specify different registries per region/environment. This way you can override only the image registry and keep the image name the same across environments.
Yes, this is syntatic sugar more than anything but it's a pattern that's been used a lot.
tests
helm template chart/atlantisand checked the resulting manifestsreferences
n/a