16 Commits (dev-v2)

Author	SHA1	Message	Date
Cristian Klein	840e0e271d	fix(tiller): improve handling of corrupted storage ... For some reason, many users experince corrupted storage with the ConfigMaps storage backend. Specifically, several Releases are marked as DEPLOYED. This patch improved handling of such situations, by taking the latest DEPLOYED Release. Eventually, the storage will clean itself out, after the corrupted Releases are deleted due to --history-max. Closes #6031 Signed-off-by: Cristian Klein <cristian.klein@elastisys.com>	6 years ago
Matt Tucker	5bf38a2d7d	fix(storage): when pruning release versions, never delete the last deployed revision ... Signed-off-by: Matt Tucker <ultimateboy@gmail.com>	7 years ago
Matthew Fisher	2d77db11fa	change copyright to "Copyright The Helm Authors"	7 years ago
Matt Butcher	0853f4906a	feat(tiller): limit number of versions stored per release ... This adds a new configuration option to Tiller to limit the number of records stored per release. Tiller stores historical release information (helm history, helm rollback). This makes it possible to set a maximum number of versions per release. To enable this feature, use `helm init --history-max NNN`. Note that because of the restrictions on Deployment objects, you will have to re-install Tiller to add a limit. Along the way, I found an unreported bug in the Memory storage driver. This fixes that bug and adds substantially more tests to catch regressions. Closes #2332	8 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	8 years ago
Maciej Kwiek	ec92b76054	Release are locked to avoid parallel changes ... Environment is supplied with release lock map which allows to lock a release by name to make sure that update, rollback or uninstall aren't running on one release at the same time.	9 years ago
Matt Butcher	a5d96c2704	fix(tiller): fix spurious "no release found" errors. ... There are some places where releases are only located if they are in the state DEPLOYED. That particular logic was incorrectly used for upgrades. That caused #1566. While fixing that issue, I found that this was also the root cause of #1587 (though because it was off by one). I added a generic method to get the last release, regardless of its status. This allows some behaviors that previously failed: - 'helm upgrade' can now be performed on a DELETED release - 'helm rollback' can now be performed on a DELETED release even if there is only one revision of that release history. Closes #1566 Closes #1587	9 years ago
fibonacci1729	e9dd302a9c	feat(helm/cmd): support for retrieving release history	9 years ago
fibonacci1729	e25732284b	feat(rollback-storage): gofmt, added missing license headers, and canconical import paths	9 years ago
fibonacci1729	383a9c186a	update pkg/storage to support rollback	9 years ago
fibonacci1729	3dca699410	fix: storage tests	9 years ago
fibonacci1729	a83425d44b	style & doc comments	9 years ago
fibonacci1729	967e438bfd	gofmt ...	9 years ago
fibonacci1729	bfd6712c94	add filtering mechanism to storage and embed Driver directly into Storage	9 years ago
fibonacci1729	aff817a1fc	run gofmt	9 years ago
fibonacci1729	4210d60c5e	add storage type to interface with multiple drivers	9 years ago