The 'app.kubernetes.io/version' label was not being rendered as
expected. It was appending onto the label before it and also
the next label label was appending onto it on the same line.

Signed-off-by: Martin Hickey <martin.hickey@ie.ibm.com>

Signed-off-by: Luis Davim <luis.davim@jet.com>

fix for unit tests

Signed-off-by: Evan Vetere <ecv@sine.com>

Signed-off-by: SataQiu <qiushida@beyondcent.com>

Signed-off-by: SataQiu <qiushida@beyondcent.com>

Signed-off-by: xichengliudui <1693291525@qq.com>

update pull request
Signed-off-by: xichengliudui <1693291525@qq.com>

update pull request
Signed-off-by: xichengliudui <1693291525@qq.com>

Signed-off-by: xichengliudui <1693291525@qq.com>

update pull request
Signed-off-by: xichengliudui <1693291525@qq.com>

Signed-off-by: xichengliudui <1693291525@qq.com>

Manifest validation is done by the builder, but it requires that the schema is set before the Stream function is called. Otherwise the StreamVisitor is created without a schema and no validation is done.

Signed-off-by: Morten Torkildsen <mortent@google.com>

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

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

Makes sure CRDs installed through the crd_install hook reaches the `established` state before the hook is considered complete.

Signed-off-by: Morten Torkildsen <mortent@google.com>

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

Signed-off-by: Pavel Eremeev <selslack@users.noreply.github.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>

There was a typo in a tiller error with "released named" message, I've changed it to "a release named". Also fix a unit-test for it.

Signed-off-by: Mikhail Kirpichev <mkirpic@gmail.com>

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

Signed-off-by: Luis Davim <luis.davim@jet.com>

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>

Signed-off-by: Jacob LeGrone <git@jacob.work>

Signed-off-by: Jacob LeGrone <git@jacob.work>

Signed-off-by: Don Bowman <db@donbowman.ca>

Signed-off-by: Vu Cong Tuan <tuanvc@vn.fujitsu.com>

Changes as per PR https://github.com/helm/helm/pull/5271



- make imagePullSecrets be an array
- move imagePullSecrets to 'root' level of Values

Signed-off-by: Don Bowman <db@donbowman.ca>

Signed-off-by: Miroslav Spousta <qiq@ucw.cz>

That the match is based on version is implicit. Making it explicit
because I had to think when I saw it.

Signed-off-by: Matt Farina <matt@mattfarina.com>

Signed-off-by: Alex Gladkikh <theshamuel@gmail.com>

when customer use --version flag, the version format include the Build
metadata, the metadata will be ingorned

Signed-off-by: jliao <jliao@alauda.io>

* fix: Update gRPC to get better TLS connection handling

To avoid backward compatibility breakers, we have been pinned to a very
old version of gRPC. But it appears that there have been some very
significant network fixes since then. Looking closely at #3480, it
appears that some of this fixes may be directly related to solving that
bug.

Note that this regenerates a few of the Go proto files, so the binary
wire format may be broken. That means this MUST be held to a minor
version, not a patch release.

To test:

- Build both client and server
- Install Tiller into your cluster
- Perform a number of Helm-Tiller interactions (`helm version`, `helm
list`)

Closes #3480

Signed-off-by: Matt Butcher <matt.butcher@microsoft.com>

* Switched to latest protobuf

Signed-off-by: Matt Butcher <matt.butcher@microsoft.com>

Signed-off-by: xichengliudui <1693291525@qq.com>

Signed-off-by: xichengliudui <1693291525@qq.com>

Signed-off-by: Gábor Lipták <gliptak@gmail.com>

Signed-off-by: Elad Iwanir <eladiw@users.noreply.github.com>

Signed-off-by: Ian Howell <ian.howell0@gmail.com>

This relates to [#3529](https://github.com/helm/helm/issues/3529

).
It adds image.pullSecret to the default generate blank chart
when the user does `helm create`.

Signed-off-by: Don Bowman <don@agilicus.com>

Signed-off-by: Arash Deshmeh <adeshmeh@ca.ibm.com>

Signed-off-by: Alexander Matyushentsev <AMatyushentsev@gmail.com>

* added test for zero values

Signed-off-by: Flavian <flavian.sierk@gmail.com>

* implemented case for zero values

Signed-off-by: Flavian <flavian.sierk@gmail.com>

* making ingress path configurations more customizable

Signed-off-by: Ahmadali Shafiee <mail@ahmadalli.net>

* update notes ingress reference

Signed-off-by: Ahmadali Shafiee <mail@ahmadalli.net>