Helm chart: add preinstall hook to env-configmap #9250
Merged
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
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.
What
The
bootloaderPod requires value from theairbyte-envConfigMap.The
bootloaderhaspre-installandpre-upgradehooks but theairbyte-envdoesn't. On a fresh install, the ConfigMap is missing when the bootloader starts.How
pre-installandpre-upgradehooks toairbyte-envConfigMaphook-weightannotation onairbyte-envandbootloaderto make sure the ConfigMap is created before thebootloaderpod runs.This fix comes from a bug detected in this Slack conversion.
Recommended reading order
charts/airbyte/templates/env-configmap.yamlcharts/airbyte/templates/bootloader/pod.yaml🚨 User Impact 🚨
No user impact.