19 Commits (812b74aca5f14ea67b531a41687abfee8a6399a6)

Author	SHA1	Message	Date
Jon Leonard	a499cf3517	Merge branch 'master' into 2751	6 years ago
jgleonard	1518f961af	fix(helm): add --render-subchart-notes flag to 'helm install' and 'helm upgrade' ... When 'helm <install|upgrade> --render-subchart-notes ...' is run, this will include the notes from the subchart when rendered via Tiller. Closes #2751 Signed-off-by: jgleonard <jgleonard@gmail.com>	6 years ago
Steve Wolter	e868da1705	Check for err before working with newRelease. (#4630) ... Should fix #4585. Signed-off-by: Steve Wolter <swolter@google.com>	6 years ago
Matthew Fisher	25a1cff317	Merge pull request #4402 from novas0x2a/force-obey-dryrun ... fix(tiller): make update --force --dry-run obey dry-run	6 years ago
Mike Lundy	0736022d98	[tiller] make update --force --dry-run obey dry-run	6 years ago
Matthew Fisher	2d77db11fa	change copyright to "Copyright The Helm Authors"	6 years ago
Arash Deshmeh	a32868e48b	added ability to handle custom release descriptions to tiller ... Signed-off-by: Arash Deshmeh <adeshmeh@ca.ibm.com>	7 years ago
Michelle Noorali	e02802ba95	ref(pkg/tiller): clarify reuseValues comment	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
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
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
Matt Butcher	88aa4def3e	Merge pull request #2701 from jascott1/i2560-hang ... fix(tiller): remove locking system from storage and rely on backend	7 years ago
Justin Scott	fa68a6e1db	fix(tiller): remove locking system from storage and rely on backend controls ... Tiller currently hangs indefinitely when deadlocks arise from certain concurrent operations. This commit removes the nested mutex locking system from pkg/Storage and relies on resource contention controls in k8s. Closes #2560	7 years ago
Aishwarya Thangappa	915e7023c4	Added more granular statuses	7 years ago
Aishwarya Thangappa	3d4361ca1f	Modified release_update and release_rollback	7 years ago
Y.W	0f953403a2	give an uniform check for release process (#2565) ... * give an uniform check for release process * fixed as the review of adamreese: update the err message when releasename is empty and update the test units. * fixed as the review of bacongobbler: add more detail information to return message. the regex rule is added to the return message.	8 years ago
Adam Reese	eccb041c0f	ref(tiller): cleanup goimports	8 years ago
Taylor Thomas	119fa6537c	feat(tiller): Adds more logging ... This builds on previous work and adds more logging to follow the full process of installing, updating, deleting, and rolling back. This also standardizes capitalization of logs and small formatting fixes	8 years ago
fibonacci1729	2ae276ae39	ref(tiller): refactor tiller APIs into logical files ... *ReleaseServer.InstallRelease -> tiller/release_install.go *ReleaseServer.UpdateRelease -> tiller/release_update.go	8 years ago