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

Add a field that allows you too deploy extra Kubernetes objects #462

Open
ubajze opened this issue Oct 11, 2024 · 0 comments · May be fixed by #471
Open

Add a field that allows you too deploy extra Kubernetes objects #462

ubajze opened this issue Oct 11, 2024 · 0 comments · May be fixed by #471

Comments

@ubajze
Copy link
Contributor

ubajze commented Oct 11, 2024

I would like to have a field (such as extraObjects for example) that would be a list where I can specify additional Kubernetes objects I want to deploy together with rest of generated objects.

Why this is needed?

  • Imagine you have secrets that are stored in an external vault (AWS Secrets Manager, HashiCorp Vault, etc.) and you want to use them. You would typically create an ExternalSecret objects which will sync secrets from a vault to the Kubernetes secrets.
  • Deploy an additional ConfigMap with settings.
  • Add Kubernetes Jobs that support your deployment (provision database, provision Redis, configure Nautobot etc.)

The benefit of using this approach is that I can use a single Helm Chart to deploy everything Nautobot related, that is not directly supported by Helm Chart and may be implementation-specific.

Some sample Helm Charts that already supported this approach:

@ubajze ubajze linked a pull request Oct 25, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant