Skip to content

Enable optional httpHeaders for controller deployment probes #78

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

Merged

Conversation

mecampbellsoup
Copy link
Contributor

Currently there is no way to configure an external service to be used for any of the *probes (liveness, readiness, startup) in the controller-deployment.

Our use-case is that we'd like to define "readiness" of our HAProxy IC to include "able to connect to a specific external service" (a database server, specifically).

This PR adds an optional httpHeaders key-values list to the 3 probes' configurable attributes per https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#http-probes.

@dkorunic
Copy link
Member

LGTM. Thanks @mecampbellsoup, merging!

@dkorunic dkorunic merged commit 8e03b38 into haproxytech:master May 11, 2021
@mecampbellsoup mecampbellsoup deleted the mc/add-host-option-for-probes branch May 11, 2021 11:40
dkorunic added a commit that referenced this pull request May 12, 2021
Changes in kubernetes-ingress:
- Add CI tests for extraEnvs
- Allow valueFrom usage with controller.extraEnvs (#80)
- Allow valueFrom usage with controller.extraEnvs (#79)
- Enable optional httpHeaders for controller deployment probes (#78)
- support auto-scaling based on custom metrics (#76)

Signed-off-by: Dinko Korunic <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants