Adding an example of extraVolumes with the Helm chart
This commit is contained in:
parent
6617e3bf01
commit
3dcc00f854
|
@ -156,6 +156,13 @@ and consider if they're appropriate for your deployment.
|
|||
configuration files from this volume with `-config-dir`. This defaults
|
||||
to false.
|
||||
|
||||
```yaml
|
||||
extraVolumes:
|
||||
- type: "secret"
|
||||
name: "consul-certs"
|
||||
load: false
|
||||
```
|
||||
|
||||
* <a name="v-server-affinity" href="#v-server-affinity">`affinity`</a> (`string`) - This value defines the [affinity](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity) for server pods. It defaults to allowing only a single pod on each node, which minimizes risk of the cluster becoming unusable if a node is lost. If you need to run more pods per node (for example, testing on Minikube), set this value to `null`.
|
||||
|
||||
```yaml
|
||||
|
@ -231,6 +238,13 @@ and consider if they're appropriate for your deployment.
|
|||
configuration files from this volume with `-config-dir`. This defaults
|
||||
to false.
|
||||
|
||||
```yaml
|
||||
extraVolumes:
|
||||
- type: "secret"
|
||||
name: "consul-certs"
|
||||
load: false
|
||||
```
|
||||
|
||||
* <a name="v-client-priorityclassname" href="#v-client-priorityclassname">`priorityClassName`</a> (`string`) - This value references an existing Kubernetes [priorityClassName](https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#pod-priority) that can be assigned to client pods.
|
||||
|
||||
* <a name="v-client-annotations" href="#v-client-annotations">`annotations`</a> (`string`) - This value defines additional annotations for client pods. This should be a formatted as a multi-line string.
|
||||
|
|
Loading…
Reference in New Issue