-
Notifications
You must be signed in to change notification settings - Fork 8
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
Allow external Helm templates #87
Labels
enhancement
New feature or request
Comments
I really like this idea +1 |
Sgitario
added a commit
that referenced
this issue
Oct 4, 2022
Sgitario
added a commit
that referenced
this issue
Oct 4, 2022
Sgitario
added a commit
that referenced
this issue
Oct 4, 2022
Sgitario
added a commit
to Sgitario/dekorate
that referenced
this issue
Oct 4, 2022
iocanel
pushed a commit
to dekorateio/dekorate
that referenced
this issue
Oct 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As an end user, I would like to provide my own templates.
At the of the day each company has its own K8s cluster configuration. Some of them have Istio and need deployments with two containers per "deployment", others could have Prometheus and need to add some extra labels to the deployments etc... Currently, I could not find a way to use my own templates based on the generated
values.yaml
in order to generate my company required k8s.yamlsNote that the
values.yaml
doesn't have any meaning by themselves, are the templates that give meaning to every values field. So, for example, a developer could set a String in a field that should be an Integer because are the templates that will handle this String and convert it into an Integer based on some custom logic.For example
Values.yaml
custom template
...and at the end are the templates that will set the right value to this field according to the company's needs.
The text was updated successfully, but these errors were encountered: