We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 Helm Chart values files in the examples directory for the most common use cases
examples
examples/helm-chart ├── README.md ├── aws-nlb │ └── values.yaml ├── something-something │ └── values.yaml ... └── read-only-fs └── values.yaml
we can then create deployment files generating them from the Helm Chart to have a single source of truth, resulting in something like:
deploy/ ├── README.md ├── aws-nlb │ └── deploy.yaml ├── something-something │ └── deploy.yaml ... └── read-only-fs └── deploy.yaml
These manifest files will have everything that's needed for the deployment in a single file, Service, Service Account, Namespace, Deployment, etc.
Service
Service Account
Namespace
Deployment
The text was updated successfully, but these errors were encountered:
During refinement, determine if we need/want the second part of this ticket.
Sorry, something went wrong.
No branches or pull requests
Add Helm Chart values files in the
examples
directory for the most common use caseswe can then create deployment files generating them from the Helm Chart to have a single source of truth, resulting in something like:
These manifest files will have everything that's needed for the deployment in a single file,
Service
,Service Account
,Namespace
,Deployment
, etc.The text was updated successfully, but these errors were encountered: