Enable shareProcessNamespace feature on airbyte-bootloader #31584
mrhovunping
started this conversation in
Connector Ideas and Features
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Request for adding shareProcessNamespace on airbyte-bootloader helm chart.
We use managed db on gcloud and to secure connexion we want to use cloud-sql-proxy. airbyte-bootloader needs a connexion to db to init everything, thus, when adding the cloud-sql-proxy sidecar, the new pod doesn't complete even if airbyte-bootloader has done his part and has exited.
The idea is to add another container as sidecar that kille the cloud-sql-proxy once airbyte-bootloader is done. To kill main process of cloud-sql-proxy container, the new container-killer needs to have accessed to the shared process (https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/)
is it something that could be added to the helm chart?
Beta Was this translation helpful? Give feedback.
All reactions