21 Commits (de7c5e5a381c47da4f6ca8da27163aa473471c8b)

Author	SHA1	Message	Date
Matt Butcher	de7c5e5a38	feat(tiller): Add .Release.Revision and .IsUpgrade ... New properties are available to template developers. Closes #1554	8 years ago
Matt Butcher	b08434aa3a	Merge pull request #1640 from technosophos/fix/1511-undeleting ... fix(*): add support for "DELETING" status	8 years ago
Matt Butcher	936028f29a	fix(*): add support for "DELETING" status ... Closes #1511	8 years ago
Adam Reese	7413320d2d	ref(kube): use a more specific interface for discovery client	8 years ago
Adam Reese	84ae1268e1	fix(*): import grouping	8 years ago
Adam Reese	7f44c116a1	ref(tiller): refactor clientset out of environment	8 years ago
Adam Reese	ea3be9e3b2	feat(*): migrate to kubernetes 1.5	8 years ago
Michelle Noorali	e3480c76e6	feat(tiller): add support for resource-policy keep ... satisfies #1326	8 years ago
Matt Butcher	02acaf125d	Merge pull request #1632 from technosophos/fix/1587-no-release-found ... fix(tiller): fix spurious "no release found" errors.	8 years ago
Adam Reese	68ff4e7b2f	Merge pull request #1636 from adamreese/fix/grpc-max-size ... fix(tiller): increase the max message size for grpc	8 years ago
Adam Reese	1f01bf51e7	fix(tiller): increase the max message size for grpc ... Increases the default message size from 4MB to 10MB.	8 years ago
Rodrigue Cloutier	f3b205c6ef	fix(*): fixed tests for Windows	8 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	8 years ago
Matt Butcher	02a1cf382c	fix(tiller): validate names before performing operations ... There were several places where an invalid name could be interpreted into a wild-card by Kubernetes. That allows Bad Things. This fix requires names to match the Kubernetes pattern for naming. Closes #1594	8 years ago
Matt Butcher	a772697f4d	Merge pull request #1560 from technosophos/fix/1528-increase-release-name-limit ... fix(tiller): allow release name to be up to 53 chars	8 years ago
Matt Butcher	9effe7a505	fix(tiller): allow release name to be up to 53 chars ... This raises the limit from 14 to 53 chars based on the Kubernetes 1.4 name limit. Closes #1528	8 years ago
Matt Butcher	985e975f53	Merge pull request #1546 from technosophos/fix/1499-show-broken-yaml ... fix(tiller): show failed YAML	8 years ago
Matt Butcher	6eabe28334	fix(tiller): show failed YAML ... When an install fails and --dry-run is set, return the broken YAML for the user to debug. Closes #1499	8 years ago
Matt Butcher	8f9b9db547	docs(tiller): add docblocks to public methods	8 years ago
Matt Butcher	3830736001	fix(tiller): improve deletion failure handling ... This does the following to improve deletion failure handling: - In an UninstallRelease operation, the release is marked DELETED as soon as the basic checks are passed. This resolves 1508. I filed a followup issue for doing this even better when we can modify protos again. - If a YAML manifest fails to parse, the error messages now suggests that the record is corrupt, and the resources must be manually deleted. - If a resource is missing during deletion, the error messages now make it clear that an object was skipped, but that the deletion continued. Closes #1508	8 years ago
adieu	c0850efeb5	Separate tiller into pkg and cmd so we can use tiller as a library.	8 years ago