192 Commits (36536d77bafb6112d820d8e768b507ca87db090e)

Author	SHA1	Message	Date
Adam Reese	36536d77ba	ref(*): remove protobuf any type	6 years ago
Adam Reese	91a6ebfed5	ref(*): remove protobuf timestamps	6 years ago
Adam Reese	6345f04190	ref(hapi): convert protobuf to go types	6 years ago
Adam Reese	68c0b6a24a	ref(proto): remove unused protobufs	7 years ago
Adam Reese	883371b8ce	ref(pkg/tiller): simplify exported methods	7 years ago
Adam Reese	8f58c9efdc	ref(*): refactor release testing	7 years ago
Adam Reese	fc4c095cf0	ref(*): remove pkg/kubernetes from tiller and storage	7 years ago
Adam Reese	496ca54183	ref(*): bypass grpc for helm client	7 years ago
Adam Reese	e9478d8f84	ref(pkg/tiller): remove ReleaseModules interface from tiller	7 years ago
Adam Reese	5715ee43d6	ref(*): bypass grpc when invoking helm list ... TODO reimplement any paging	7 years ago
Adam Reese	62804848c6	ref(pkg/tiller): refactor out imports of pkg/helm	7 years ago
Arash Deshmeh	c22492ff01	fix(helm): refactor tiller release install unit tests using chart and install request stubs ... Signed-off-by: Arash Deshmeh <adeshmeh@ca.ibm.com>	7 years ago
Nikhil Manchanda	b687e9e879	Merge pull request #3709 from adshmh/fix-output-leak-of-tiller-release-install-test ... fix output leak from tiller release install test	7 years ago
Taylor Thomas	2a86164c1d	Merge pull request #3829 from stuartleeks/set-rollback-failure ... Fix: Failed rollback left in PENDING_ROLLBACK state	7 years ago
Michelle Noorali	72d54f356d	Merge pull request #3831 from michelleN/fix-3655 ... fix(pkg/tiller): saves all previous computed values on reuseValues	7 years ago
Michelle Noorali	e02802ba95	ref(pkg/tiller): clarify reuseValues comment	7 years ago
Michelle Noorali	9266731dc4	fix(pkg/tiller): reuseValues combines all prev val ... Resolves #3655 We were seeing that when running helm upgrade with the reuse-values flag enabled that you could end up in the position where overrides a.k.a computed values from previous revisions were not being saved on the updated revision. This left us in a weird position where some computed values would disappear mysteriously in the abyss. That happened because computed values from previous revisions weren't merged with the new computed values every time the reuse-values flag was used. This PR merges computed values from the previous revisions so you don't end up in that kind of conundrum.	7 years ago
Stuart Leeks	bac4f45f94	Switch flag to update existing record	7 years ago
Matthew Fisher	e794c48c3a	Merge pull request #3540 from flant/hook_recreate_delete_policy ... Implement before-hook-creation delete policy	7 years ago
Timofey Kirillov	b7fe0d0bd7	Add hook-delete-policy ReleaseServer unit tests ... Cover hook-succeeded, hook-failed and before-hook-creation hook delete policies.	7 years ago
fibonacci1729	ad99c1b749	release list paritioning	7 years ago
fibonacci1729	2dd9b34d28	stream releases when listing	7 years ago
Alexey igrychev	1d4883bf3c	Implement before-hook-creation delete policy ... Existing helm.sh/hook-delete-policy annotation variables (hook-failed, hook-succeeded) do not allow to leave failed jobs for debugging without blocking the next job launching: every failed job must be deleted manually before the next related release is launching (installing, updating or rolling back). New policy, before-hook-creation, removes the hook from previous release if there is one before the new hook is launched and can be used with another variable.	7 years ago
Arash Deshmeh	a43ddcc191	fix output leak from tiller release install test ... Signed-off-by: Arash Deshmeh <adeshmeh@ca.ibm.com>	7 years ago
Matthew Fisher	13730b0dab	replace FAILED deployments with `helm upgrade --install --force` ... 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.	7 years ago
Johnny Bergström	5f1a21bc32	fix(tiller): Supersede multiple deployments (#3539) ... * 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	7 years ago
Matthew Fisher	1a9e0f0d15	Merge pull request #3535 from adshmh/fix-output-leak-from-pkg-tiller-tests ... fix the output leak from test code under pkg/tiller	7 years ago
Arash Deshmeh	5b25eef9e2	fix(helm): fix the bug in test code under pkg/tiller that leaks output to stdout during build ... Signed-off-by: Arash Deshmeh <adeshmeh@ca.ibm.com>	7 years ago
Johnny Bergström	98e5006ecf	Bump client side grpc max msg size ... Set it to match the server side, or the default limit of 4MB will still apply when upgrading charts. Fixes #3512	7 years ago
Matt Farina	614cd9dfe7	fix(grpc): Fixes issue where message sending limited to 4mb ... 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.	7 years ago
xuhaigang	61623bfe2d	feat(tiller/proto):Allow charts to specify k8s compatibility in semver field ... Add an optional field kubeVersion to Chart.yaml that allows the chart developer to specify a semver compliant version. Closes #2708, #2706	7 years ago
Adam Reese	a31e3b8fe1	ref(*): kubernetes v1.9 support (#3234)	7 years ago
Taylor Thomas	04769b7c26	Merge pull request #3131 from fgimenez/fix-2745 ... check if resource is present before adding it to remaining or keep on deletion	7 years ago
Federico Gimenez	a607fe798d	iinitialize message only when at least one manifest is kept	7 years ago
Federico Gimenez	93bce130fb	fix signatures	7 years ago
Federico Gimenez	81eaf2f263	only check existence for the possibly kept manifests	7 years ago
Hadrien Chauvin	838d780894	update google.golang.org/grpc to 1.7.2 (#3101)	7 years ago
Federico Gimenez	e6d907ed28	check if resource is present before adding it to remaining or keep on deletion	7 years ago
Adam Reese	82ef751414	fix(tiller): upgrade last deployed release ... Fixes #2437 Two bugs were causing this behavior - Tiller was marking the previous release superseded when an upgrade failed. - Upgrade was diffing against failed releases	7 years ago
Taylor Thomas	29c3b5276f	fix(tiller): Adds CRD ordering ... This adds CRD ordering into the explicit kind sorter list Closes #2925	7 years ago
Matthew Fisher	d4f5a133dd	Merge pull request #2960 from HotelsDotCom/upgrade-failure-record-release-as-update ... Correctly persists Release upgrade failure	7 years ago
Taylor Thomas	f8e9741578	Merge pull request #2984 from thomastaylor312/feat/add_missing_test ... fix(sorter): Adds missing unit test	7 years ago
Justin Scott	b642ba2087	Merge pull request #2831 from jascott1/sort_unknown_kind ... bug(tiller): sort unknown but different kinds alphabetically based on kind name	7 years ago
Taylor Thomas	333f8dd354	fix(sorter): Adds missing unit test ... Adds a unit test that was missed as part of #2961	7 years ago
Maxim Ivanov	ff5acc9bd8	Make Memory driver to store copy of releases to stop hiding storage errors during tests	7 years ago
NauxLiu	c3f9120e02	Load StorageClass before PersistentVolume is loaded.	7 years ago
Maxim Ivanov	38c3f58dca	Correctly persists Release upgrade failure ... When release upgrade fails, updatedRelease is already created in a storage by *ReleaseServer.UpdateRelease, therefore we should be updating it's status, not creating it again.	7 years ago
Justin Scott	ed24b3199a	bug(tiller): sort unknown but different kinds alphabetically based on kind name ... Adds additional manifest sorting logic so that different unknown kinds are sorted alphabetically so that manifest order is more deterministic.	7 years ago
Steven E. Harris	f588315b76	Remove spurious field in kind sorter test (#2667) ... The test never reads the manifest type's "content" field, so there's no reason to populate it explicitly with its zero value.	7 years ago
Matthew Fisher	bb5db61325	Merge pull request #2781 from jascott1/i2755-template ... feat(helm): add `template` command	7 years ago