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

[bitnami/grafana-operator] spec.config.security.auth in body must be of type string: "object" #25235

Closed
fabio-s-franco opened this issue Apr 19, 2024 · 5 comments · Fixed by #25467
Assignees
Labels
grafana-operator solved tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@fabio-s-franco
Copy link
Contributor

fabio-s-franco commented Apr 19, 2024

Name and Version

bitnami/grafana-operator 4.1.0

What architecture are you using?

amd64

What steps will reproduce the bug?

Install the chart using the values.yaml file and uncomment the auth section:

    security:
      # ## Grafana Admin credentials, if omitted they will be admin:<random_pass>
      # admin_user:
      # admin_password:
      #
      # ## OIDC configuration
      # ##
      # auth:
      #   disable_login_form: "false"
      #   disable_signout_menu: "false"
      # auth.generic_oauth:
      #   enabled: "true"
      #   client_id: grafana
      #   client_secret: a391df94-dd1f-46d6-b3ab-60e90f23e8a2
      #   scopes: profile email
      #   auth_url: https://keycloak.example.com/auth/realms/master/protocol/openid-connect/auth
      #   token_url: https://keycloak.example.com/auth/realms/master/protocol/openid-connect/token
      #   api_url: https://keycloak.example.com/auth/realms/master/protocol/openid-connect/userinfo
cannot patch "grafana-operator-grafana" with kind Grafana: Grafana.grafana.integreatly.org "grafana-operator-grafana" is invalid: [spec.config.security.auth.anonymous: Invalid value: "object": spec.config.security.auth.anonymous in body must be of type string: "object"]

On a side note, the links here are broken.

Are you using any custom parameters or values?

Just as described on the reproduction, uncommenting any of the auth sections will trigger the error. ie:

    security:
      # ## Grafana Admin credentials, if omitted they will be admin:<random_pass>
      # admin_user:
      # admin_password:
      #
      # ## OIDC configuration
      # ##
      auth:
        disable_login_form: "false"
        disable_signout_menu: "false"
      # auth.generic_oauth:
      #   enabled: "true"
      #   client_id: grafana
      #   client_secret: a391df94-dd1f-46d6-b3ab-60e90f23e8a2
      #   scopes: profile email
      #   auth_url: https://keycloak.example.com/auth/realms/master/protocol/openid-connect/auth
      #   token_url: https://keycloak.example.com/auth/realms/master/protocol/openid-connect/token
      #   api_url: https://keycloak.example.com/auth/realms/master/protocol/openid-connect/userinfo

What is the expected behavior?

Chart installs / updates without errors

What do you see instead?

cannot patch "grafana-operator-grafana" with kind Grafana: Grafana.grafana.integreatly.org "grafana-operator-grafana" is invalid: [spec.config.security.auth.anonymous: Invalid value: "object": spec.config.security.auth.anonymous in body must be of type string: "object"]
@fabio-s-franco fabio-s-franco added the tech-issues The user has a technical issue about an application label Apr 19, 2024
@github-actions github-actions bot added the triage Triage is needed label Apr 19, 2024
@carrodher
Copy link
Member

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

@fabio-s-franco
Copy link
Contributor Author

Hi @carrodher thank you for the encouragement, I will give it a shot.

@fabio-s-franco
Copy link
Contributor Author

@carrodher here is the PR: #25467

@carrodher
Copy link
Member

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!

@fabio-s-franco
Copy link
Contributor Author

Thank you, now that I went through the hardest part, which had nothing to do with the fix itself, it will be easier for future contributions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment