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
After debugging for some time, I've realized these charts use the lookup function when using a userDefinedSecret to get the secret data to be used in other chart logic. This generally goes against helm best practices and is entirely unsupported in systems like ArgoCD for GitOps managed clusters.
Proposed solution:
If the customer is using userDefinedSecret, assume the secret values are correct to render the helm chart. Don't have logic in the chart that depends on the lookup function to contact the k8s API.
The text was updated successfully, but these errors were encountered:
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
After debugging for some time, I've realized these charts use the lookup function when using a userDefinedSecret to get the secret data to be used in other chart logic. This generally goes against helm best practices and is entirely unsupported in systems like ArgoCD for GitOps managed clusters.
argoproj/argo-cd#5202
Proposed solution:
If the customer is using userDefinedSecret, assume the secret values are correct to render the helm chart. Don't have logic in the chart that depends on the lookup function to contact the k8s API.
The text was updated successfully, but these errors were encountered: