-
Notifications
You must be signed in to change notification settings - Fork 68
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
Get certificate from Key Vault in kubernetes.io/tls secret type #821
Labels
Comments
Thank you @RichardChen820. If I understand your proposal, it can handle several secrets and of different types in only one |
@antoineozenne-at-leocare It supports generating TLS type Secrets in the latest v1.3.0, please check this doc for the detail. |
Close this issue, feel free to reactivate if you have more questions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is it possible to get a certificate from Key Vault in a
kubernetes.io/tls
secret type? For now, I have a PFX certificate in a Key Vault. When I reference it in theAzureAppConfigurationProvider
resource, I get it in aOpaque
secret type, in a binary format (base64 encoded). I would like to get my certificate in akubernetes.io/tls
secret type (in a PEM format) to be able to use it with ingress-nginx for example.This way, I could replace all my
SecretProviderClass
resources by only oneAzureAppConfigurationProvider
to get all my configuration (configuration and secrets), for each of my applications. I find thatAzureAppConfigurationProvider
is more comfortable and easy to use thanSecretProviderClass
.The text was updated successfully, but these errors were encountered: