Open federicochiesa opened 5 days ago
Hi!
Could you run kubectl get secrets
to see if there is a secret created for the external database?
There was this secret:
Name: keycloak-externaldb
Namespace: default
Labels: app.kubernetes.io/instance=keycloak
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=keycloak
app.kubernetes.io/version=26.0.6
helm.sh/chart=keycloak-24.2.2
Annotations: meta.helm.sh/release-name: keycloak
meta.helm.sh/release-namespace: default
Type: Opaque
Data
====
db-password: 20 bytes
I tried to delete it along with everything else and start from scratch, but I get the same exact error and the secret reappeared.
The secret contained the correct password for the DB.
Ok, so, looking at the values, I see that you set namespaceOverride: sso
. That means that the namespace should be sso
and not default, right?
I think I found the issue:
In keycloak/templates/secret-external-db.yaml
, instead of
namespace: {{ .Release.Namespace | quote }}
it should be:
namespace: {{ include "common.names.namespace" . | quote }}
As you spotted the issue, would you like to submit a PR with the fix?
Thank you! I just did.
Thank you! The team will take a look
Name and Version
bitnami/keycloak 24.2.2
What architecture are you using?
amd64
What steps will reproduce the bug?
kubectl describe pod keycloak-0 -n sso
Are you using any custom parameters or values?
What is the expected behavior?
It should connect to the DB using the provided values, which are the same as indicated in the readme.
What do you see instead?