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

An option to set additional annotations and service account names for the MongoDb cfg service #361

Open
virtyaluk opened this issue Aug 18, 2024 · 0 comments

Comments

@virtyaluk
Copy link

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 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.

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