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
I'm trying to access a Helm chart from a private repository within my company, and I've followed the Helmfile documentation for passing credentials. However, I encountered an issue where I could only retrieve the Helm chart when the username and password were specified as plain text.
Since vals is a project associated with Helmfile, it seems logical to integrate vals directly within Helmfile for handling sensitive information. Here's how I've attempted to configure it:
In this configuration, I'm using ref+awssecrets to reference credentials from AWS Secrets Manager. However, it appears that this approach does not work as expected for authenticating with the private repository.
Is there a recommended way to use vals with Helmfile for securely passing credentials, or am I missing something in the configuration? Any guidance or suggestions would be appreciated.
The text was updated successfully, but these errors were encountered:
I'm trying to access a Helm chart from a private repository within my company, and I've followed the Helmfile documentation for passing credentials. However, I encountered an issue where I could only retrieve the Helm chart when the username and password were specified as plain text.
Since vals is a project associated with Helmfile, it seems logical to integrate vals directly within Helmfile for handling sensitive information. Here's how I've attempted to configure it:
In this configuration, I'm using ref+awssecrets to reference credentials from AWS Secrets Manager. However, it appears that this approach does not work as expected for authenticating with the private repository.
Is there a recommended way to use vals with Helmfile for securely passing credentials, or am I missing something in the configuration? Any guidance or suggestions would be appreciated.
The text was updated successfully, but these errors were encountered: