[Feature Request] Allow definition of existing secret for Avi configuration

[ron1]

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

[swathinsankaran]

@ron1 are you using --generate-name with helm install?

[ron1]

@swathinsankaran No.

[swathinsankaran]

Thanks, @ron1 for the reply.

[itaytalmi]

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.