Why not use a deployment's readinessProbe for healthchecks?

[clayvan]

I tried doing some searching and didn't find much, so forgive me if this gets asked a lot.

Is it possible to use a deployment's readinessProbe instead of defining healthcheck annotations on the Ingress object?

It seems like there's an unnecessary duplication of the healthcheck path/port when the information is already available through the K8s API.

It would be cool to see annotations something like

alb.ingress.kubernetes.io/healthcheck-path: use-readiness-probe
alb.ingress.kubernetes.io/healthcheck-port: use-readiness-probe

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[vnugent]

I'm also confused about the duplication of K8s health checks and those defined as annotations.

[sergeyshevch]

/reopen
I also guess that we can just use k8s readiness probe (if it exists) that contain same health check functional.
I can work on it if someone can tell more about reasons of this behaviour

[k8s-ci-robot]

@sergeyshevch: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen
I also guess that we can just use k8s readiness probe (if it exists) that contain same health check functional.
I can work on it if someone can tell more about reasons of this behaviour

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[gazal-k]

would one of the contributors please comment on whether this is feasible? We pretty much duplicate our readinessProb config to health check annotations. It would be nice to streamline it, make it more k8s native perhaps. In my opinion the annotations are always meant for functionality additional to the spec, but readinessProbes already exist in the spec for the same purpose.