-
Notifications
You must be signed in to change notification settings - Fork 345
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
Document using cloudsql auth proxy in kubernetes jobs #1941
Comments
You can do this with two flags:
With both in place, your main task has to call the This is a common enough use case, we'll make this issue about improving documentation about it. Let me know if you have any other questions. |
Hello, There will soon be a better piece of documentation on how to make this work correctly in the cloud-sql-proxy-operator project. See cloud-sql-proxy-operator#438. I will add documentation to this project as well, for users who would rather configure side-car containers themselves. |
This example demonstrates how to use the /quitquitquit endpoint in a kubernetes job to allow job pods to exit successfully when the main application container exits. Fixes #1941
I experienced a similar issue. Upon completion, the main container shuts down and makes the recommended The
This is described in the comments of the example EDIT: Line 15 in cc76a54
|
Yes, GET support was released in 2.7.0. https://github.com/GoogleCloudPlatform/cloud-sql-proxy/releases/tag/v2.7.0 |
Awesome, thank you! Appreciate all the hard work on the |
Question
I need to use this in a kubernetes job,
While it works in the side car pattern, the job is stuck in NotReady status since the auth proxy never exit.
any way to trigger an exit code with status code that will make the job succeed?
Code
No response
Additional Details
No response
The text was updated successfully, but these errors were encountered: