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

The secret type "opaque" does not convert to the Kubernetes secret type "Opaque" #77

Open
AliaksandrShamchonak opened this issue May 27, 2024 · 0 comments

Comments

@AliaksandrShamchonak
Copy link

Every document located on the webpage https://akv2k8s.io/reference/azure-key-vault-secret/ focuses solely on presenting information regarding the secret type identified as "opaque". However, as per the authoritative rules and guidelines established by Kubernetes and available on their official documentation page https://kubernetes.io/docs/concepts/configuration/secret/#secret-types, the specified secret type for Kubernetes should be correspondingly tagged as "Opaque".
Furthermore, it is possible to insert any secret type in spec.output.secret.type, following which the resource creation will be executed. In simple terms, there is no process in place to verify the type of resource created.

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