-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Kubernetes: Liveness/Readiness check for external Endpoints Services #8147
Comments
Dear traefik team, Is there any solution that you could provide to anwser our needs? But I would prefere using CRD resources. Would be possible to have the same level of feature between the CRD and the file provider for Service objects ? Thanks Marc |
If someone from the community wants to contribute on this, the maintainers team would love to support & help :) |
Hi @emilevauge, Are we in line that the need is to be able to use a CRD type TraefikService, in order to replace the following configuration in file ?
|
I will try to do a PR soon to handle service LoadBalancer type from CRD. |
Hello @ChristianCiach and thanks for opening this issue, We missed during the triage that we had another issue about adding the HeatlhCheck feature for external services in K8S. To keep discussions focused on only one issue I am closing this one as a duplicate of #8541 as it contains details on how the issue can be solved, as well as a corresponding draft pull request. |
Traefik
IngressRoute
has no support for health checks. Unfortunately, the issue #6492 has been closed with this comment:As we can read here, Kubernetes has no support for health checks of headless services (with custom
Endpoints
) or services of typeExternalName
: kubernetes/kubernetes#77738 (comment)This leaves us with the unsatisfying situation that it is currently impossible to have health checks for external services when using the KubernetesCRD provider.
I see no good reason for omitting this feature from KubernetesCRD and forcing people to use the file provider instead.
Please see the comments starting at #6492 (comment) for further use-cases of this feature.
The text was updated successfully, but these errors were encountered: