Charts on your computer

Desktop app only When you’re working on a chart, you can deploy it straight from your computer: change a template, review the dry run against the real cluster, upgrade. KubeStacks shows what the chart is, checks it with helm lint against your values, and remembers it for the next time.

​

Choose the chart

In Upgrade… or Install chart, pick A chart on this computer. Then either:

• Choose… → Chart folder… or Packaged chart (.tgz)…, or
• type its path and press ↵. ~/ works, like ~/charts/web.

KubeStacks reads the chart with helm show chart, and shows its name, version, app version and description. It warns you when something looks off:

​

Subcharts

If the chart has dependencies that aren’t in its charts/ folder yet, KubeStacks lists them: “Its charts/ folder is missing redis 19.0.1.” Download dependencies runs helm dependency update on the folder, then checks the chart again. A packaged .tgz has its dependencies inside already.

​

Values files beside it

Charts often keep values for each environment next to values.yaml, and test values in ci/. For a chart folder, Load values from… offers each of them: Every .yaml or .yml file in the chart’s folder except Chart.yaml and values.yaml, and every one in its ci/ folder, is listed. Picking one loads it into the editor, where you can change it before reviewing. The file itself isn’t changed.

​

helm lint, before every review

KubeStacks runs helm lint on the chart with the values in the editor, and shows what it found: “helm lint found no problems”, or a count of errors and warnings with each message. Check again runs it once more, against the values as they are now. It also runs again every time you press Review, so you never review a dry run of a chart you haven’t linted, and its findings show next to the manifest diff.

​

It remembers

When you upgrade or install a release from a chart on your computer, KubeStacks remembers which one. The next Upgrade… of that release starts on A chart on this computer, with the same path, so iterating is: edit, Upgrade…, Review, Upgrade. The path is kept per cluster, namespace and release, on this computer.