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.

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

Keycloak fails to deploy when prometheusRule.enabled = true #632

Closed
noahpb opened this issue Aug 2, 2024 · 3 comments · Fixed by #633
Closed

Keycloak fails to deploy when prometheusRule.enabled = true #632

noahpb opened this issue Aug 2, 2024 · 3 comments · Fixed by #633
Assignees
Labels
bug Something isn't working ci Issues pertaining to CI / Pipelines / Testing sso Issues related to the SSO stack (Keycloak/Authservice)

Comments

@noahpb
Copy link
Contributor

noahpb commented Aug 2, 2024

Environment

Device and OS: OS X/Colima
App version: v0.24.1
Kubernetes distro being used: k3d

Steps to reproduce

  1. Deploy uds-core with an override for keycloak that specifies prometheusRule.enabled=true

Expected result

uds-core deploys Keycloak successfully with a PrometheusRule object

Actual Result

      WARNING  Retrying (1/3) in 5s: unable to complete the helm chart install/upgrade: template:
               keycloak/templates/prometheusrule.yaml:7:24: executing
               "keycloak/templates/prometheusrule.yaml" at <.Release.Namespace>: nil pointer evaluating
               interface {}.Namespace

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

low

Additional Context

Should we be introducing additional testing to our packages? This feature is not enabled by default or tested in ci. There may be other features that are disabled by default that are currently escaping validation.

Relates #231

@noahpb noahpb added the possible-bug Something may not be working label Aug 2, 2024
@noahpb noahpb self-assigned this Aug 2, 2024
@noahpb noahpb mentioned this issue Aug 2, 2024
5 tasks
@noahpb noahpb added bug Something isn't working sso Issues related to the SSO stack (Keycloak/Authservice) ci Issues pertaining to CI / Pipelines / Testing and removed possible-bug Something may not be working labels Aug 2, 2024
@mjnagel
Copy link
Contributor

mjnagel commented Aug 2, 2024

Should we be introducing additional testing to our packages? This feature is not enabled by default or tested in ci. There may be other features that are disabled by default that are currently escaping validation.

I think for Keycloak this is an especially valid concern. Other components we pull in are largely upstream, and we do test most of the specifics that we layer in (istio, netpols, etc). For Keycloak, however, we built the custom config image and the chart so we should have more holistic coverage of at least all the templates.

@mjnagel
Copy link
Contributor

mjnagel commented Aug 2, 2024

For this specific issue the namespace ref needs to be de-scoped to outside of the with block (.Release.Namespace -> $.Release.Namespace). May be other template problems, but that's the immediate failure.

We may want to consider commenting out/dropping this template though unless we see a strong need for it AND add a validation of it in CI or our internal environment.

@noahpb
Copy link
Contributor Author

noahpb commented Aug 2, 2024

Started a draft PR here to fix the immediate issue. I'm in favor of dropping the template if its irrelevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ci Issues pertaining to CI / Pipelines / Testing sso Issues related to the SSO stack (Keycloak/Authservice)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants