zitadel-charts: [Bug]: masterkey or masterkeySecretName values not recognized when used in an umbrella Chart
Preflight Checklist
- I could not find a solution in the documentation, the existing issues or discussions
- I have joined the ZITADEL chat
Version
7.6.0
App version
No response
Describe the problem caused by this bug
Hello, I’m trying to deploy zitadel with argoCD using app-of-apps pattern using umbrella charts. Structure is: zitadel-folder – chart.yaml – values.yaml
The issue is that masterkey doesn’t seem to be recognised when deployed in this way
The 2 screenshots are taken using the file present at https://github.com/zitadel/zitadel-charts/blob/main/examples/2-postgres-secure/zitadel-values.yaml I’ve tested with a personal values file or either with one of the example provided in the git in the example folder. Still same error either setting masterkey or masterkeySecretName values. This is not the first app I deploy in this way, i have about 20.
To reproduce
- set up argocd
- set up app-of-apps pattern
- create a folder for zitadel and the chart and values files
- deploy
Logs
No response
Expected behavior
Be able to deploy zitadel
Relevant Configuration
K8s version: rke2 ArgoCD version: 2.9.5
Additional Context
this is my personal values.yaml
zitadel:
replicaCount: 2
masterkeySecretName: zitadel-masterkey
configmapConfig:
Database:
Postgres:
Host: postgres-cluster-zitadel-rw.svc.cluster.local
Port: 5432
Database: zitadel
MaxOpenConns: 20
MaxIdleConns: 10
MaxConnLifetime: 30m
MaxConnIdleTime: 5m
User:
Username: zitadel
SSL:
Mode: verify-full
Admin:
Username: postgres
SSL:
Mode: verify-full
dbSslUserCrtSecret: zitadel-cluster-user-cert
service:
type: LoadBalancer
# If service type is "ClusterIP", this can optionally be set to a fixed IP address.
clusterIP: ""
port: 8080
protocol: http2
annotations: {}
metrics:
enabled: true
serviceMonitor:
# If true, the chart creates a ServiceMonitor that is compatible with Prometheus Operator
# https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#monitoring.coreos.com/v1.ServiceMonitor.
# The Prometheus community Helm chart installs this operator
# https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack#kube-prometheus-stack
enabled: true
Fro reference this is the manifest i’m using https://github.com/ilbarone87/testing
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 17 (8 by maintainers)
I got it now. Because you define zitadel in an umbrella chart as a dependency that you call zitadel, you also need to specify the dependencies values under the yaml property that matches your dependencies name.
So your umbrella values should look similar to this:
If this also doesn’t work, I’ll reopen the issue again.
I think next week I have time to check it
@fforootd also I think the problem is restricted to when the helm install requires to run dependency build before as the repo is pulled from remote in my Chart.yaml. For some reason doesn’t like that build. Indeed if I git clone your chart in my local and have all the templates yaml available in the same folder there is no issue.