luxolus/open-consul
2
0
Fork 0
Code Issues 1 Pull requests Packages Releases Wiki Activity

Update docs for Helm chart maxUnavailable value

Browse source 
Due to a Helm templating limitation, setting this value to `0` requires
an extra flag when installing. This adds information about that.
This commit is contained in:
Rebecca Zanzig 2018-11-09 16:58:54 -08:00
parent 0b7b3cbd41
commit bd5ecc4828
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
website/source/docs/platform/k8s/helm.html.md
View file

@ -168,7 +168,10 @@ and consider if they're appropriate for your deployment.
* <a name="v-server-disruptionbudget-maxunavailable" href="#v-server-disruptionbudget-maxunavailable">`maxUnavailable`</a> (`integer: null`) -
The maximum number of unavailable pods. By default, this will be automatically
computed based on the `server.replicas` value to be `(n/2)-1`.
computed based on the `server.replicas` value to be `(n/2)-1`. If you need to set
this to `0`, you will need to add a `--set 'server.disruptionBudget.maxUnavailable=0'`
flag to the helm chart installation command because of a limitation in the Helm
templating language.
- <a name="v-server-extraconfig" href="#v-server-extraconfig">`extraConfig`</a> (`string: "{}"`) -
A raw string of extra JSON or HCL configuration for Consul servers. This