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
Background:
I have N number of clusters, and I'm deploying the same helm chart to all of them. Some will need a cluster-specific secret, while the rest can use a shared secret. In the ArgoCD Application/Set I can define multiple helm values files with the ignoreMissingValueFiles option set. This allows me to use an "overwrite" pattern for cluster-specific customization effectively.
Problem:
When using the AVP plugin I lose access to ignoreMissingValueFiles. I'm wondering if others have run into this and what their solutions are. I'd like to maintain my existing pattern of just defining overwrite value file per cluster (when needed) rather than needing to edit the helm chart directly when we add/change clusters.
For additional context this is what my argocd chart/value structure looks like:
Hello,
Background:
I have N number of clusters, and I'm deploying the same helm chart to all of them. Some will need a cluster-specific secret, while the rest can use a shared secret. In the ArgoCD Application/Set I can define multiple helm values files with the
ignoreMissingValueFiles
option set. This allows me to use an "overwrite" pattern for cluster-specific customization effectively.Problem:
When using the AVP plugin I lose access to
ignoreMissingValueFiles
. I'm wondering if others have run into this and what their solutions are. I'd like to maintain my existing pattern of just defining overwrite value file per cluster (when needed) rather than needing to edit the helm chart directly when we add/change clusters.For additional context this is what my argocd chart/value structure looks like:
. ├── apps │ ├── chart1 │ ├── chart2 │ └── chartn └── values ├── cluster1 │ └── chart1 │ └── overwrite-values.yaml ├── cluster2 │ └── chart2 │ └── overwrite-values.yaml ├── clustern │ └── chartn │ └── overwrite-values.yaml
The text was updated successfully, but these errors were encountered: