Thanks

0.5.1 (2018-11-21)

Bug fixes

Helm releases will now stay put when an upgrade fails or the
Kubernetes API connectivity is flaky, instead of getting purged
weaveworks/flux#1530

Thanks

Thanks to @sfrique, @brantb and @squaremo for helping document the
issues leading to this bug fix, @stefanprodan for actually squashing
the bug and all others that may have gone unnoticed while writing this
release note.

0.5.0 (2018-11-14)

WARNING: this release of the Helm operator is not backward-compatible:

It uses a new custom resource HelmRelease, and will ignore
FluxHelmRelease resources

To use it, you will need to migrate custom resources to the new format
supported by this version. See the upgrade
guide.

This version of the Helm operator supports HelmRelease custom
resources, which each specify a chart and values to use in a Helm
release, as in previous versions. The main improvement is that you are
now able to specify charts from Helm repos, as well as from git repo,
per resource (rather than a single git repo, which is supplied to the
operator).

0.4.0 (2018-11-01)

This release improves support for TLS connections to Tiller; in
particular it makes it much easier to get server certificate
verification (--tiller-tls-verify) to work.

It also adds the ability to supply additional values to
FluxHelmRelease resources by attaching Kubernetes secrets. This
helps with a few use cases:

supplying the same default values to several releases

providing secrets (e.g., a password) to a chart that expects them as values

using values files without inlining them into FluxHelmReleases

NB It is advised that you deploy the operator alongside Tiller
v2.10 or more recent. To properly support TLS, the operator now
includes code from Helm v2.10, and this may have difficulty connecting
to older versions of Tiller.

Bug fixes

Make --tiller-tls-verify work as intended, by giving better
instructions, and adding the argument --tiller-tls-hostname which
lets you specify the hostname that TLS should expect in the
certificate
weaveworks/flux#1484

Improvements

You can now create secrets containing a values.yaml file, and
attach them to a FluxHelmRelease as additional values to use
weaveworks/flux#1468

Bug fixes

Improvements

The operator now runs helm dep build for charts before installing
or upgrading releases. This will use a lockfile if present, and
update the dependencies according to requirements.yaml otherwise
weaveworks/flux#1450

A new flag --git-timeout controls how long the Helm operator will
allow for git operations
weaveworks/flux#1416

The Helm operator image now includes the Helm command-line client,
which makes it easier to troubleshoot problems using kubectl exec
(as part of
weaveworks/flux#1450)

0.2.1 (2018-09-17)

This is a patch release that allows helm-op to recover from a failed release install.
If a chart is broken, Tiller will reserve the name and mark the release as failed.
If at a later time the chart is fixed, helm-op can’t install it anymore because the release name is in use.
Purging the release after each failed install allows helm-op to keep retrying the install.