KubeLinter is a static analysis tool that checks Kubernetes YAML files and Helm charts to ensure the applications represented in them adhere to best practices.
Description of the problem/feature request
Allow kube-linter to receive an arbitrary amount of values.yaml files (just like helm upgrade does) when checking a helm chart.
Description of the existing behavior vs. expected behavior
We deploy several "variations" of the same workload across environments, and those variations we control via values.yaml.
We have a baseline behavior (no added values), and then with --values %the-file%.yml we enable/disable extra features for that environment.
We'd like to catch potential errors on the chart when using those special files too.
And that would load the default values.yaml inside the helm-chart directory as well as merging the values defined in custom.yaml on top of the aforementioned.
Description of the problem/feature request Allow
kube-linterto receive an arbitrary amount ofvalues.yamlfiles (just likehelm upgradedoes) when checking a helm chart.Description of the existing behavior vs. expected behavior
We deploy several "variations" of the same workload across environments, and those variations we control via
values.yaml.We have a baseline behavior (no added values), and then with
--values %the-file%.ymlwe enable/disable extra features for that environment.We'd like to catch potential errors on the chart when using those special files too.
Additional context
Something like:
And that would load the default
values.yamlinside thehelm-chartdirectory as well as merging the values defined incustom.yamlon top of the aforementioned.I'm open to contribute this change!