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
Is your feature request related to a problem? Please describe.
I am unable to use an existing secret generated by a Secrets Manager such as the external-secret operator for the AKO avi-secret.
Describe the solution you'd like
The ako Helm Chart currently captures avicredentials properties and uses them to generate a Secret named avi-secret. In some environments, it is preferred to allow definition of an existing secret rather than the generation of a new secret.
In order to support this case, consider introducing a new Helm property entitled avicredentials.existingSecret. See PR https://github.com/grafana/helm-charts/pull/542/files for a similar feature that was implemented in the Grafana Loki Helm Chart.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
ron1
changed the title
Allow definition of existing secret for Avi configuration
[Feature Request] Allow definition of existing secret for Avi configuration
May 22, 2023
Hi, any updates on this? The usage of an existing secret makes a lot of sense. The current state where Helm expects the credentials to be directly specified in the values.yaml imposes a security risk.
Is your feature request related to a problem? Please describe.
I am unable to use an existing secret generated by a Secrets Manager such as the external-secret operator for the AKO
avi-secret
.Describe the solution you'd like
The ako Helm Chart currently captures
avicredentials
properties and uses them to generate a Secret namedavi-secret
. In some environments, it is preferred to allow definition of an existing secret rather than the generation of a new secret.In order to support this case, consider introducing a new Helm property entitled
avicredentials.existingSecret
. See PR https://github.com/grafana/helm-charts/pull/542/files for a similar feature that was implemented in the Grafana Loki Helm Chart.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: