Signed-off-by: Steven Sheehy <ssheehy@firescope.com>

Fix `no RESOURCE with the name NAME found`

feat: make tiller probeAddr configurable

Fix description of helm dependency command

Don't print ROLLING BACK if atomic is not set

As many people have requested and discussed in #3159.

The variable name are kept the same as before. Corresponding command-line flag is named, and description are written, after the existing flag for gRPC.

The scope of this change is intentionally limited to the minimum. That is, I have not yet added `--probe=false`, because it shouldn't be a blocker if we can change the port number.
Signed-off-by: Yusuke KUOKA <ykuoka@gmail.com>

Signed-off-by: Timofey Kirillov <timofey.kirillov@flant.com>

Signed-off-by: Timofey Kirillov <timofey.kirillov@flant.com>

Fixed default value for `helm.sh/chart` label

Signed-off-by: Sergey Kozlov <mail.sergey.kozlov@gmail.com>

Fixed typos in docs/chart_best_practices

Signed-off-by: Sergey Kozlov <mail.sergey.kozlov@gmail.com>

Document update | variable representation change

Signed-off-by: Arvind Kumar <10303369+aku163@users.noreply.github.com>

Fixed a typo in docs

Replaced `chart` command by `helm`.
Signed-off-by: Sergey Kozlov <mail.sergey.kozlov@gmail.com>

closes #5544 don't do multiple chart reads on upgrade

Signed-off-by: Joschka Tillmanns <joschka@tillmanns.me>

chore(glide): bump kubernetes to 1.14

Signed-off-by: Matthew Fisher <matt.fisher@microsoft.com>

Signed-off-by: Xiangxuan Liu <xiangxuan.liu@rightcapital.com>

Signed-off-by: Mike Eves <michael.eves@autotrader.co.uk>

refactor(*): make "not found" error message user-friendly

Signed-off-by: Pavel Eremeev <selslack@users.noreply.github.com>

Update golang version

Signed-off-by: ialidzhikov <i.alidjikov@gmail.com>

remove kubernetes from contributing section

Signed-off-by: Devin Burnette <devin.burnette@betterment.com>

Signed-off-by: Timofey Kirillov <timofey.kirillov@flant.com>

This is the fix for only one particular, but important case.

The case when a new resource has been added to the chart and
there is an error in the chart, which leads to release failure.
In this case after first failed release upgrade new resource will be
created in the cluster. On the next release upgrade there will be the error:
`no RESOURCE with the name NAME found` for this newly created resource
from the previous release upgrade.

The root of this problem is in the side effect of the first release process,
Release invariant says: if resouce exists in the kubernetes cluster, then
it should exist in the release storage. But this invariant has been broken
by helm itself -- because helm created new resources as side effect and not
adopted them into release storage.

To maintain release invariant for such case during release upgrade operation
all newly *successfully* created resources will be deleted in the case
of an error in the subsequent resources update.

This behaviour will be enabled only when `--cleanup-on-fail` option used
for `helm upgrade` or `helm rollback`.
Signed-off-by: Timofey Kirillov <timofey.kirillov@flant.com>

fix(script): follow redirected URL of github latest release

Closes #5480
Signed-off-by: Arief Hidayat <mr.arief.hidayat@gmail.com>

When checking version and desired version is not set, we follow
redirected URL of github latest release to get the latest tag instead of
trying to get the tag value from html content.

Closes #5480
Signed-off-by: Arief Hidayat <mr.arief.hidayat@gmail.com>

style: fix golint error in init.go for redundant err!=nil check

update kubernetes deps to latest patch releases

Update outdated docs image for google storage permissions

Signed-off-by: tariqibrahim <taibrahi@microsoft.com>

fix(scripts): use a more precise method of grepping

Github recently changed the output of the releases page.

grepping for the exact <a> tag fixes the issue where the wrong tag was being filtered.
Signed-off-by: Matthew Fisher <matt.fisher@microsoft.com>

fix(tiller): fixed a typo in tiller and unit test