Skip to content

Commit d47c774

Browse files
authored
Update: properly align columns
1 parent a3c86f0 commit d47c774

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/deployment/helm.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -339,15 +339,15 @@ API's you need to install the prometheus operator in your cluster.
339339
| `gc.extraArgs` | array | [] | Additional [command line arguments](../reference/gc-commandline-reference.md) to pass to nfd-gc |
340340
| `gc.extraEnvs` | array | [] | Additional environment variables to pass to nfd-gc |
341341
| `gc.revisionHistoryLimit` | integer | | Specify how many old ReplicaSets for this Deployment you want to retain. [revisionHistoryLimit][revisionhistorylimit] |
342-
| `gc.livenessProbe.initialDelaySeconds` | integer | 10 | Specifies the number of seconds after the container has started before liveness probes are initiated. |
343-
| `gc.livenessProbe.failureThreshold` | integer | 3 (by Kubernetes) | Specifies the number of consecutive failures of liveness probes before considering the pod as not ready. |
342+
| `gc.livenessProbe.initialDelaySeconds` | integer | 10 | Specifies the number of seconds after the container has started before liveness probes are initiated. |
343+
| `gc.livenessProbe.failureThreshold` | integer | 3 (by Kubernetes) | Specifies the number of consecutive failures of liveness probes before considering the pod as not ready. |
344344
| `gc.livenessProbe.periodSeconds` | integer | 10 (by Kubernetes) | Specifies how often (in seconds) to perform the liveness probe. |
345345
| `gc.livenessProbe.timeoutSeconds` | integer | 1 (by Kubernetes) | Specifies the number of seconds after which the probe times out. |
346-
| `gc.readinessProbe.initialDelaySeconds` | integer | 5 | Specifies the number of seconds after the container has started before readiness probes are initiated. |
346+
| `gc.readinessProbe.initialDelaySeconds` | integer | 5 | Specifies the number of seconds after the container has started before readiness probes are initiated. |
347347
| `gc.readinessProbe.failureThreshold` | integer | 3 (by Kubernetes) | Specifies the number of consecutive failures of readiness probes before considering the pod as not ready. |
348348
| `gc.readinessProbe.periodSeconds` | integer | 10 (by Kubernetes) | Specifies how often (in seconds) to perform the readiness probe. |
349349
| `gc.readinessProbe.timeoutSeconds` | integer | 1 (by Kubernetes) | Specifies the number of seconds after which the probe times out. |
350-
| `gc.readinessProbe.successThreshold` | integer | 1 (by Kubernetes) | Specifies the number of consecutive successes of readiness probes before considering the pod as ready. |
350+
| `gc.readinessProbe.successThreshold` | integer | 1 (by Kubernetes) | Specifies the number of consecutive successes of readiness probes before considering the pod as ready. |
351351
| `gc.dnsPolicy` | array | ClusterFirstWithHostNet | Garbage collector pod [dnsPolicy][dnspolicy] |
352352

353353
<!-- Links -->

0 commit comments

Comments
 (0)