This commits adds the possibility to back Tiller (or the future
Tiller-less Helm CLI) with any SQL database (only postgres has been
tested so far) to store release information.
The main motivation for this commit was to use a storage backend that
would allow releases larger that 1MB in size (ConfigMap or Secret
drivers don't, because of limits on value size in the underlying etcd
key-value store).
Signed-off-by: Étienne Lafarge <etienne.lafarge@gmail.com>
Co-authored-by: Elliot Maincourt <e.maincourt@gmail.com> (@emaincourt)
Co-authored-by: Paul Borensztein <hi@0x01.fr> (@commit-master)
* Snap installation information added
Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
* Moved Snap instructions to the different section
Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
* first staging
* Filled out RBAC and TLS
* Finished draft.
* smoothing
* gRPC endpoint tooling moved up and cleaned
* updating install.md
* addressed comments; will continue expanding and iterating
This feature enables users to specify more control over where Tiller pod
lands by allowing "node-selectors" to be specified. Alternatively, the
"--output" flag will skip install and dump Tiller's raw Deployment manifest to stdout so user may alter it as they see fit (probably with a JSON manipulation tool like jq).
Closes#2299
The user needs to get all of the way down to developers docs to
realize they need glide, but if you follow a user who doesn't
necessarily want to develop but wants to build from source, you'd
follow this path:
README -> Quick Start -> Releases -> . o O (Source doesn't work)
-> Install
And then you'd realize that you need Glide.
This one-liner patch fixes that. :)