Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow overwrite tlsExistingSecretName data key names #190

Open
avnerv opened this issue Jul 4, 2023 · 0 comments
Open

Allow overwrite tlsExistingSecretName data key names #190

avnerv opened this issue Jul 4, 2023 · 0 comments

Comments

@avnerv
Copy link

avnerv commented Jul 4, 2023

Since we are using the k8s cert-manager to generate certificates, we face a limitation where modifying the data key names within the k8s secret, which is generated by the cert-manager, is not possible.
Considering this restriction, we need the option to overwrite the k8s secret data key names that you expect for in the helm chart:

  # Specifies an existing secret for tls-certificate must include:
  # - akeyless-api-cert.crt (base64)
  # - akeyless-api-cert.key (base64)

https://github.com/akeylesslabs/helm-charts/blob/main/charts/akeyless-api-gateway/values.yaml#L297-L300

Additionally, add the support of secret type kubernetes.io/tls

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant