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.
I'd like the ability to configure livenessProbes on the consul-client daemonset container as well as the ability to override the default readinessProbe. This is due to a networking bug unrelated to consul that liveness/readiness probes would allow for better monitoring.
Feature Description
The Helm chart should support configuring container livenessProbe and readinessProbe
Community Note
Is your feature request related to a problem? Please describe.
I'd like the ability to configure livenessProbes on the consul-client daemonset container as well as the ability to override the default readinessProbe. This is due to a networking bug unrelated to consul that liveness/readiness probes would allow for better monitoring.
Feature Description
The Helm chart should support configuring container livenessProbe and readinessProbe
Use Case(s)
Contributions
Yes, I've raised #4388
The text was updated successfully, but these errors were encountered: