Skip to content
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.

Sign up for GitHub

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

Jump to bottom

feature: Set scheme for probes and serviceMonitor #784

Merged
merged 1 commit into from
Aug 23, 2024
Merged

feature: Set scheme for probes and serviceMonitor #784

merged 1 commit into from
Aug 23, 2024

Commits on Aug 6, 2024

  1. feature: Set scheme for probes and serviceMonitor 

    The new health endpoints used by the three probes (liveness, readiness
and startup) as well as the metrics endpoint are now served on a
dedicated interface with its own port. The scheme of the interface only
servers HTTP or HTTPS. If the main keycloak interface serves HTTPS,
the internal management interface will also serve HTTPS, regardless if
the main keycloak interface servers plain HTTP or not.

It's therefore impossible for the probes or the serviceMonitor to work
with a plain HTTP scheme, if keycloak has HTTPS enabled.

We therefore need a way to specify the scheme of the internalPort via
helm values to be able to set a custom scheme for the probes and the
serviceMonitor

Signed-off-by: Nicolas Bigler <[email protected]>
    @TheBigLee
    TheBigLee committed Aug 6, 2024
    Configuration menu
    Copy the full SHA
    30cb39e View commit details
    Browse the repository at this point in the history