Skip to content
GitLab
user avatar
fix(helm): Merge nested values correctly on upgrade (#4806)
Morten Torkildsen authored 
Upgrading a release and override existing values doesn't work as expected for nested values. Maps should be merged recursively, but currently maps are treated just like values and replaced at the top level.

If the existing values are:
```yaml
resources:
  requests:
    cpu: 400m
  something: else
```
and an update is done with ```--set=resources.requests.cpu=500m```, it currently ends up as
```yaml
resources:
  requests:
    cpu: 500m
```
but it should have been
```yaml
resources:
  requests:
    cpu: 500m
  something: else
```

This PR updates the way override values are merged into the existing set of values to merge rather than replace maps.

Closes: #4792

Signed-off-by: default avatarMorten Torkildsen <mortent@google.com>
82d01cb3
Select Git revision
  • main default
  • dependabot/go_modules/github.com/docker/distribution-2.8.2incompatible
  • dependabot/go_modules/golang.org/x/crypto-0.9.0
  • dependabot/go_modules/golang.org/x/term-0.8.0
  • dependabot/go_modules/github.com/lib/pq-1.10.9
  • dependabot/go_modules/github.com/rubenv/sql-migrate-1.4.0
  • dependabot/go_modules/k8s.io/klog/v2-2.100.1
  • release-3.12
  • release-3.11
  • release-3.10
  • Release
  • release-3.9
  • release-3.8
  • release-3.7
  • release-3.6
  • release-3.6.2
  • release-3.6.1
  • release-3.5
  • release-3.4
  • add-codeql
  • v3.12.0
  • v3.12.0-rc.1
  • v3.11.3
  • v3.11.2
  • v3.12.0-dev.1
  • v3.11.1
  • v3.11.0
  • v3.11.0-rc.2
  • v3.11.0-rc.1
  • v3.10.3
  • v3.10.2
  • v3.10.1
  • v3.10.0
  • v3.10.0-rc.1
  • v3.9.4
  • v3.9.3
  • v3.9.2
  • v3.9.1
  • v3.9.0
  • v3.9.0-rc.1
History Find file
Clone
Name Last commit Last update
.circleci
.github
_proto
cmd
docs
pkg
rootfs
scripts
testdata
.appveyor.yml
.gitignore
CONTRIBUTING.md
LICENSE
Makefile
OWNERS
README.md
SECURITY_CONTACTS
code-of-conduct.md
glide.lock
glide.yaml
versioning.mk
README.md

Helm

CircleCI Go Report Card GoDoc

Helm is a tool for managing Kubernetes charts. Charts are packages of pre-configured Kubernetes resources.

Use Helm to:

  • Find and use popular software packaged as Helm charts to run in Kubernetes
  • Share your own applications as Helm charts
  • Create reproducible builds of your Kubernetes applications
  • Intelligently manage your Kubernetes manifest files
  • Manage releases of Helm packages

Helm in a Handbasket

Helm is a tool that streamlines installing and managing Kubernetes applications. Think of it like apt/yum/homebrew for Kubernetes.

  • Helm has two parts: a client (helm) and a server (tiller)
  • Tiller runs inside of your Kubernetes cluster, and manages releases (installations) of your charts.
  • Helm runs on your laptop, CI/CD, or wherever you want it to run.
  • Charts are Helm packages that contain at least two things:
    • A description of the package (Chart.yaml)
    • One or more templates, which contain Kubernetes manifest files
  • Charts can be stored on disk, or fetched from remote chart repositories (like Debian or RedHat packages)

Install

Binary downloads of the Helm client can be found on the Releases page.

Unpack the helm binary and add it to your PATH and you are good to go!

If you want to use a package manager:

  • Homebrew users can use brew install kubernetes-helm.
  • Chocolatey users can use choco install kubernetes-helm.
  • GoFish users can use gofish install helm.

To rapidly get Helm up and running, start with the Quick Start Guide.

See the installation guide for more options, including installing pre-releases.

Docs

Get started with the Quick Start guide or plunge into the complete documentation

Roadmap

The Helm roadmap uses Github milestones to track the progress of the project.

Community, discussion, contribution, and support

You can reach the Helm community and developers via the following channels:

Code of conduct

Participation in the Helm community is governed by the Code of Conduct.