-
Notifications
You must be signed in to change notification settings - Fork 993
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
Feature Request: Support Running Sidecar With a Command #2448
Comments
tabbyl21
added a commit
to tabbyl21/postgres-operator
that referenced
this issue
Oct 17, 2023
This PR addresses issue zalando#2448 . Some containers may not have entry points, if this is the case they would need to be run using a command. This change extends the definition of sidecar so that there is an optional command field. If the field is present then the container will be run using that command. This is a two line change that is fully backward compatible.
PR with required changes: #2449 |
Any updates? |
FxKu
pushed a commit
that referenced
this issue
Dec 23, 2024
* Feat: Support Running Sidecard with a Command. This PR addresses issue #2448 . Some containers may not have entry points, if this is the case they would need to be run using a command. This change extends the definition of sidecar so that there is an optional command field. If the field is present then the container will be run using that command. This is a two line change that is fully backward compatible.
#2449 has been merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I would like to support running a sidecar using a command. This is useful in the case that the container being run as a sidecar does not have an entry point and needs to be run explicitly using a command.
Here are my answers to the requested questions:
I have run the change on my own fork, it is a two liner change. :)
The text was updated successfully, but these errors were encountered: