You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking for ways to set additional pod annotations and service account names for the cfg statefulset service created by the MongoDB operator. I'm using a 3rd party mutation webhook that intercepts the pod-creating flow to insert sensitive data from the Vault secrets store in place of referenced Kubernetes secret values (basically every time it runs into a Valut-specific syntax in place of a secret value, it'd then call Vault API to retrieve a real secret value and replace original value). The webhook behavior is configured through pod annotations and the default account name. Since the cfg service is responsible (I presume) for the creation of default MongoDB users, I need the cfg service to come with Vault configuration for it to know how to talk to the Vault cluster. I couldn't find any configuration options in the helm value files. Is there any at all? If not, will it be possible to expand the configuration options to include the cfg set of options just like there is one for the rs0?
Thanks.
The text was updated successfully, but these errors were encountered:
Hello there!
I'm looking for ways to set additional pod annotations and service account names for the
cfg
statefulset service created by the MongoDB operator. I'm using a 3rd party mutation webhook that intercepts the pod-creating flow to insert sensitive data from the Vault secrets store in place of referenced Kubernetes secret values (basically every time it runs into a Valut-specific syntax in place of a secret value, it'd then call Vault API to retrieve a real secret value and replace original value). The webhook behavior is configured through pod annotations and the default account name. Since thecfg
service is responsible (I presume) for the creation of default MongoDB users, I need thecfg
service to come with Vault configuration for it to know how to talk to the Vault cluster. I couldn't find any configuration options in the helm value files. Is there any at all? If not, will it be possible to expand the configuration options to include thecfg
set of options just like there is one for thers0
?Thanks.
The text was updated successfully, but these errors were encountered: