7517d3161c
This change has been tested by the promenade resiliency gate. This adds configuration for which ports to use for the tiller container in the bootstrap-armada pod, and changes the defaults to be outside of `net.ipv4.ip_local_port_range`, since the apiserver container in this pod dynamically selects ports in that range to connect to etcd, which can cause conflicts. See [0] for an example. By default, since we're no longer using the standard tiller ports, this does mean that we cannot connect to this tiller instance (before it's replaced by the chart-based instance) via the helm CLI, until it supports overriding the tiller port to connect to, however this should be relatively soon [1]. [0]: https://github.com/helm/helm/issues/4886 [1]: https://github.com/helm/helm/pull/5590 Change-Id: Ief11411f079db27489e6974c028f6b7a16bb67bf |
||
|---|---|---|
| .. | ||
| configuration | ||
| troubleshooting | ||
| api.rst | ||
| conf.py | ||
| design.rst | ||
| developer-onboarding.rst | ||
| exceptions.rst | ||
| getting-started.rst | ||
| index.rst | ||