-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(helm): Add option to deploy extra containers to init job #25783
feat(helm): Add option to deploy extra containers to init job #25783
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not aware of how cloud-sql-auth-proxy works, but looking at the docs, shouldn't this go to deployment.yaml instead? since it's a sidecar?
@dpgaspar yes that's correct and the deployment.yaml has |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
SUMMARY
Adds extraContainers to init job pob.
This is required if for example connecting to an external database using the Cloud SQL Auth Proxy as a sidecar.