[bitnami/keycloak] Clarification on KEYCLOAK_MANAGEMENT_PASSWORD

[steveardis]

Name and Version

bitnami/keycloak

What architecture are you using?

amd64

What steps will reproduce the bug?

I'm raising this issue for clarification on the usage of the KEYCLOAK_MANAGEMENT_PASSWORD. We recently upgraded the Keyclaok Helm chart for bitnami/keycloak from version 3.1.1 to 21.1.2. My understanding is that, somewhere between these versions, WildFly was replaced by Quarkus. It is also my understanding that the management-password property was specifically for WildFly. After rotating the management-password property in Azure Key Vault and updating our Kubernetes secrets, everything still seems functional, which further confirms my belief that the management-password is no longer used.

However, the documentation at https://github.com/bitnami/charts/tree/main/bitnami/keycloak/#installing-the-chart, still references the KEYCLOAK_MANAGEMENT_PASSWORD.

Am I misunderstanding the usage of the management-password?

Are you using any custom parameters or values?

No response

What is the expected behavior?

No response

What do you see instead?

References to KEYCLOAK_MANAGEMENT_PASSWORD at https://github.com/bitnami/charts/tree/main/bitnami/keycloak/#installing-the-chart. I would not have expected there to be references to a management-password since WildFly is no longer used.

Additional information

No response

[migruiz4]

Hi @steveardis,

Thank you for reporting this, the README.md has been updated in this PR #25996 which I think fixes your issue.