Fix tolerations and topologySpreadConstraints default values (#10643)

Signed-off-by: Fran Mulero <fmulero@vmware.com>
This commit is contained in:
Fran Mulero
2022-06-07 15:32:22 +02:00
committed by GitHub
parent 94402c8ddb
commit b70cdb9991
3 changed files with 3 additions and 3 deletions

View File

@@ -23,4 +23,4 @@ name: sealed-secrets
sources:
- https://github.com/bitnami/bitnami-docker-sealed-secrets
- https://github.com/bitnami-labs/sealed-secrets
version: 1.0.5
version: 1.0.6

View File

@@ -131,7 +131,7 @@ The command removes all the Kubernetes components associated with the chart and
| `tolerations` | Tolerations for Sealed Secret pods assignment | `[]` |
| `updateStrategy.type` | Sealed Secret statefulset strategy type | `RollingUpdate` |
| `priorityClassName` | Sealed Secret pods' priorityClassName | `""` |
| `topologySpreadConstraints` | Topology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template | `{}` |
| `topologySpreadConstraints` | Topology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template | `[]` |
| `schedulerName` | Name of the k8s scheduler (other than default) for Sealed Secret pods | `""` |
| `terminationGracePeriodSeconds` | Seconds Redmine pod needs to terminate gracefully | `""` |
| `lifecycleHooks` | for the Sealed Secret container(s) to automate configuration before or after startup | `{}` |

View File

@@ -232,7 +232,7 @@ priorityClassName: ""
## @param topologySpreadConstraints Topology Spread Constraints for pod assignment spread across your cluster among failure-domains. Evaluated as a template
## Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/#spread-constraints-for-pods
##
topologySpreadConstraints: {}
topologySpreadConstraints: []
## @param schedulerName Name of the k8s scheduler (other than default) for Sealed Secret pods
## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
##