Closes #3088

(cherry picked from commit d8489901)

When using `helm upgrade --install`, if the first release fails, Helm will respond with an error saying that it cannot upgrade from an unknown state.

With this feature, `helm upgrade --install --force` automates the same process as `helm delete && helm install --replace`. It will mark the previous release as DELETED, delete any existing resources inside Kubernetes, then replace it as if it was a fresh install. It will then mark the FAILED release as SUPERSEDED.

(cherry picked from commit 13730b0d)

* add test for rolling back from a FAILED deployment

* Update naming of release variables

Use same naming as the rest of the file.

* Update rollback test

- Add logging
- Verify other release names not changed

* fix(tiller): Supersede multiple deployments

There are cases when multiple revisions of a release has been
marked with DEPLOYED status. This makes sure any previous deployment
will be set to SUPERSEDED when doing rollbacks.

Closes #2941 #3513 #3275

(cherry picked from commit 5f1a21bc)

The docs say: use DialContext instead.

(cherry picked from commit 9bac0a4c)

Set it to match the server side, or the default limit
of 4MB will still apply when upgrading charts.

Fixes #3512

(cherry picked from commit 98e5006e)

(cherry picked from commit 3b22ecd5)

https://github.com/kubernetes/helm/pull/3183 added a keepalive to the Helm client of 30s period, while Tiller was never configured to permit this, keeping the default minimum keepalive period of 5 minutes, disconnecting any clients which ping more regularly than this.

This commit enforces a minimum that is lower than what Helm is configured for, preventing these disconnections, and thus fixes #3409.

(cherry picked from commit 588f7a84)

Between grpc 1.2.x and 1.7.x there was an API change. The
previous MaxMsgSize is now a wrapper around MaxRecvMsgSize. This
change now sets the MaxRecvMsgSize and MaxSendMsgSize which need
to be set independently.

(cherry picked from commit 614cd9df)

This reverts commit 371ff8f2.

(cherry picked from commit f13c4d28)

CRDs and other objects seen as unstructured cannot use strategic
merge patching. It has never been supported on CRDs. Previously,
cases like unstructured objects could have caused an unregistered
error. This is no longer the case.

This change explicitly looks for unstructured objects and handles
those using json merge patching.

Closes #3382

(cherry picked from commit e6137ff0)

(cherry picked from commit 4947e5aa)

(cherry picked from commit ea520afd)

(cherry picked from commit 3d05da01)

(cherry picked from commit b065ffe1)

(cherry picked from commit 2cee4c68)

While we still don't want to upload to GCS/GCR, we also don't want the CI run to fail because we are just skipping the step. This is most usually seen in the `release-X.Y` branches cut every minor release.

(cherry picked from commit d28d1756)

also add it to the release checklist.

(cherry picked from commit 8604e0b8)

the release branch was of the format `release-vX.Y.Z` when it should be `release-X.Y`.

(cherry picked from commit 4763cca8)

Added k8comp plugin for helm

helm template: display the default value of --kube-version in help message

This commit improves to display the default value of --kube-version in
help message of `helm template` command.

```
--kube-version string    kubernetes version used as Capabilities.KubeVersion.Major/Minor (default "1.9")
```

Adding mattfarina to the OWNERS file

fix(ci): install zip

feat Making starter templates more versatile

Add helm-monitor plugin

fix(capabilities): Adding GitVersion to default set

Added a --wait flag to helm init

Added a --wait flag for helm init which pings the Tiller server and ensures that it is ready to receive requests
Fixes #2114
Signed-off-by: Alex Johnson <ajohnson@bombora.com>

Add SlickNik to OWNERS

Add AppVersion to initial chart

Update initial chart experience

Prior to this, using the semver template functions with the full
version, which is represented in the GitVersion, was not possible
for helm template and lint commands because the property was not
populated by default. This update adds default handling.

Closes #3349

feat(pkg/helm): allow concurrent requests on a shared client