Skip to content

skipper-ingress: disable automated healthcheck routes #9241

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

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

ponimas
Copy link
Collaborator

@ponimas ponimas commented Apr 14, 2025

Skipper provides two flags to control kubernetes healthcheck routes:
-kubernetes-healthcheck (true by default) that enables automatic healthcheck routes
and -reverse-source-predicate to select source predicate type.

Currently when routesrv is enabled (default state) it adds
automatic healthcheck routes and appends default filters to
all routes including healthcheck routes.

We want to avoid adding default filters to healthcheck routes. The explicit inlined checks were created in this PR.
This change disables automatic healthcheck routes provided by routesrv.

This PR should be merged only after this one is deployed.

@ponimas ponimas added the major Major feature changes or updates, e.g. feature rollout to a new country, new API calls. label Apr 14, 2025
@ponimas ponimas force-pushed the skipper/inline-kube-health-2 branch from c736504 to d6efa24 Compare April 14, 2025 19:39
@ponimas ponimas force-pushed the skipper/inline-kube-health-disable-checks-at-routeserv branch from 5e38359 to 758162c Compare April 14, 2025 19:42
@ponimas ponimas changed the title skipper-ingress: explicit healthcheck routes pt.2 skipper-ingress: disable automated healthcheck routes Apr 14, 2025
@ponimas ponimas force-pushed the skipper/inline-kube-health-2 branch from d6efa24 to 2c8324b Compare April 22, 2025 12:34
@ponimas ponimas force-pushed the skipper/inline-kube-health-disable-checks-at-routeserv branch from 758162c to 97ab99a Compare April 22, 2025 12:35
@ponimas ponimas marked this pull request as ready for review April 22, 2025 12:40
@ponimas ponimas force-pushed the skipper/inline-kube-health-2 branch from 2c8324b to 362d805 Compare April 23, 2025 08:56
@ponimas ponimas force-pushed the skipper/inline-kube-health-disable-checks-at-routeserv branch from 97ab99a to d7df0bb Compare April 23, 2025 08:56
@ponimas ponimas force-pushed the skipper/inline-kube-health-2 branch 3 times, most recently from 1484a5e to be20c54 Compare April 25, 2025 09:05
@ponimas ponimas force-pushed the skipper/inline-kube-health-disable-checks-at-routeserv branch from d7df0bb to 1f2aad7 Compare April 25, 2025 09:07
Base automatically changed from skipper/inline-kube-health-2 to dev April 25, 2025 13:01
@ponimas ponimas force-pushed the skipper/inline-kube-health-disable-checks-at-routeserv branch from 1f2aad7 to 84f7a84 Compare April 25, 2025 14:17
ponimas added 2 commits May 2, 2025 12:09
Skipper provides two flags to control kubernetes healthcheck routes:
`-kubernetes-healthcheck` (true by default) that enables automatic healthcheck routes
and `-reverse-source-predicate` to select source predicate type.

Currently when routesrv is enabled (default state) it adds
automatic healthcheck routes and appends default filters to
all routes including healthcheck routes.

We want  to avoid adding default filters to healthcheck routes. The explicit inlined checks were created in #9206
This change disables automatic healthcheck routes provided by routesrv.

This reverts commit d6efa24.

Signed-off-by: Aleksandr Ponimaskin <[email protected]>
Remove the conditional configuration for IPv6 healthcheck CIDR
whitelisting for routeserv in the skipper deployment manifest. This
option is no longer necessary as the healthchecks are moved to the
skipper-ingress level.

Signed-off-by: Aleksandr Ponimaskin <[email protected]>
@ponimas ponimas force-pushed the skipper/inline-kube-health-disable-checks-at-routeserv branch from 84f7a84 to 2f2fd1d Compare May 2, 2025 10:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge major Major feature changes or updates, e.g. feature rollout to a new country, new API calls.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants