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'd like to pull avi credentials from a vault and then create a secret with those credentials. This can be achieved using sealed-secrets.
The problem is, ako doesn't wait for the secret to appear and use it, instead it just creates its own secret overwriting the secret if it already exists.
Describe the solution you'd like
Allow a secretName: to be specified rather than require the secret to be added to the values.yaml in order to be used.
avicredentials:
# specify an existing secret to use, otherwise a secret will be created automatically
existingSecretName: "<secretName>"
# if an 'existingSecretName' was not specified, the following values will be used to create a secret named 'avi-secret'
username: ""
password: ""
authtoken: ""
# certificateAuthorityData: |
# PEM-encoded public certificate of avi server with Common Name attribute set as the FQDN of the avi server
If 'existingSecretName' is empty then use the passed in values, otherwise expect a secret with the name 'secretName' to exist with the needed values.
(a) Also allow an initContainer to be specified so that I can add an initContainer which will wait for the secret to appear. This can be added by adding the vmware 'common' library as a dependency to this helm chart. Like so:
lknite
changed the title
Update helm chart to allow a secret to be specified
[Feature Request] Update helm chart to allow a secret to be specified
Jan 24, 2024
Is your feature request related to a problem? Please describe.
I'd like to pull avi credentials from a vault and then create a secret with those credentials. This can be achieved using sealed-secrets.
The problem is, ako doesn't wait for the secret to appear and use it, instead it just creates its own secret overwriting the secret if it already exists.
Describe the solution you'd like
If 'existingSecretName' is empty then use the passed in values, otherwise expect a secret with the name 'secretName' to exist with the needed values.
Describe alternatives you've considered
I tried creating the 'avi-secret' secret prior to deploying ako but it was simply overwritten.
Additional context
ESXI 8u2, Tanzu, K8s version v1.26.5
The text was updated successfully, but these errors were encountered: