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 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:
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?
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:
extraObjects
)extraDeploy
)The text was updated successfully, but these errors were encountered: