You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, the Secret has a fix name: that means, it's not possible to run two DTRs in the same K8s namespace.
To Reproduce
Deploy the helm chart to a k8s cluster with enableKeycloak: false
Run kubectl get secret keycloak-database-credentials
Expected behavior
If I disable the keycloak setup, I don't want to have anything polluting my environment in context of the keycloak setup.
Possible Implementation
Add an if statement to the template based on the value enableKeycloak. Additionally use a generated name based on the release name (like it's done at the registry/registry-deployment.yaml)
Additional notes
I already created a similary issue recarding the configmap for keycloak: #124
The text was updated successfully, but these errors were encountered:
Describe the bug
With the current helm chart the file
charts/registry/templates/keycloak/database-credentials.yaml
will always be deployed to the cluster - doesn't matter if keycloak was enabled or not.Additionally, the Secret has a fix name: that means, it's not possible to run two DTRs in the same K8s namespace.
To Reproduce
enableKeycloak: false
kubectl get secret keycloak-database-credentials
Expected behavior
If I disable the keycloak setup, I don't want to have anything polluting my environment in context of the keycloak setup.
Possible Implementation
Add an if statement to the template based on the value
enableKeycloak
. Additionally use a generated name based on the release name (like it's done at theregistry/registry-deployment.yaml
)Additional notes
I already created a similary issue recarding the configmap for keycloak: #124
The text was updated successfully, but these errors were encountered: