You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Is your feature request related to a problem? Please describe.
Implement annotation globally and/or per Pod where we can tell consul-k8s to inject the consul-dataplane container in initContainers with the restartPolicy: Always. Thinking about it, this is the only thing that needs to be done to have the consul-dataplane run before the main containers and also to NOT block shutdown of Jobs.
Use Case(s)
Solve a whole slew of issues which we have to now manually work around with shutdown delays and startup checks in the main container.
Contributions
The text was updated successfully, but these errors were encountered:
Community Note
Is your feature request related to a problem? Please describe.
Yes, very similar to the corresponding vault-k8s ask here: hashicorp/vault-k8s#620
See: https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/
Feature Description
Implement annotation globally and/or per Pod where we can tell consul-k8s to inject the
consul-dataplane
container ininitContainers
with therestartPolicy: Always
. Thinking about it, this is the only thing that needs to be done to have theconsul-dataplane
run before the main containers and also to NOT block shutdown of Jobs.Use Case(s)
Solve a whole slew of issues which we have to now manually work around with shutdown delays and startup checks in the main container.
Contributions
The text was updated successfully, but these errors were encountered: