Add shareProcessNamespace to bootloader helm chart #282
+26
−0
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
Solved: #31697
In case you need to implement a sidecar pod that needs to be killed once the bootloader is completed. Example sidecar to connect to db (gcp auth proxy):
Create a pod with 3 containers:
If you don't have this mechanism bootloader pod will still be ready, even if bootloader container is in completed state because Cloud SQL Auth Proxy container is still up and airbyte deployment process will be stuck.
How
Add shareProcessNamespace feature into the bootloader helm chart (https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/)
Recommended reading order
Can this PR be safely reverted / rolled back?
🚨 User Impact 🚨
No