Many credentials are being used in the deployments like username and password/identity secrets for peers, orderers, CAs, etc. Along with passing these values as plaintext in helm values file, there should be an option to read these values from kubernetes secrets (like many vendor helm charts offer).
The creation of these secrets is up to the user, weather they create them manually or via some operator like External Secrets Operator.
This will directly help towards the "Manage secrets with secrets management services like Vault, AWS Secrets manager, etc" feature goal.
Example:
The Values file will look something like this:
identity_name: xyz
identity_secret: abc
# Name of the secret resource to take the above two values from. The keys have to be exactly same as above.
identityCredsFromSecret: identity_secret #<--- This is the name of the secret resource where the identity_name and identity_secret is mentioned
Many credentials are being used in the deployments like username and password/identity secrets for peers, orderers, CAs, etc. Along with passing these values as plaintext in helm values file, there should be an option to read these values from kubernetes secrets (like many vendor helm charts offer).
The creation of these secrets is up to the user, weather they create them manually or via some operator like External Secrets Operator.
This will directly help towards the "Manage secrets with secrets management services like Vault, AWS Secrets manager, etc" feature goal.
Example:
The Values file will look something like this: