feat: Add annotation to provision public secret data only #676
+386
−244
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements stackabletech/issues#547, based on decision in https://github.com/stackabletech/decisions/issues/78.
This PR introduces a new annotation for secret volumes, called
secrets.stackable.tech/tbdwhich allows users to only request public/non-sensitive data instead of the complete secret material like currently. For backwards compatibility, this defaults tofalse(potentially different value based on decision).The following use-cases are now supported:
autoTlsbackend, but only provision theca.crt/truststore.p12for the consumer.kerberosKeytabbackend, but only provision thekrb5.conffor the consumerk8sSearchbackend to select Secrets which contain non-sensitive data only and support parsing the partial set of files. Explicitly requesting a format currently fails due to stricter parsing. This strict parsing is disabled whensecrets.stackable.tech/tbdis usedThe following example details the last use-case mentioned above:
(Note: The CA was generated by the default
tlsSecretClass)