diff --git a/Chart.yaml b/Chart.yaml index f29ea4c38..5650ed8ee 100644 --- a/Chart.yaml +++ b/Chart.yaml @@ -4,6 +4,6 @@ description: Helm chart for installing ONLYOFFICE Docs in Kubernetes type: application -version: 4.2.0 +version: 4.2.1 -appVersion: 8.1.0 +appVersion: 8.1.1 diff --git a/README.md b/README.md index ea66d8fef..76e80a73c 100644 --- a/README.md +++ b/README.md @@ -492,9 +492,7 @@ The `helm delete` command removes all the Kubernetes components associated with | `converter.annotations` | Defines annotations that will be additionally added to Converter Deployment. If set to, it takes priority over the `commonAnnotations` | `{}` | | `converter.podAnnotations` | Map of annotations to add to the Converter deployment pods | `rollme: "{{ randAlphaNum 5 \| quote }}"` | | `converter.replicas` | Converter replicas quantity. If the `converter.autoscaling.enabled` parameter is enabled, it is ignored | `2` | -| `converter.updateStrategy.type` | Converter deployment update strategy type | `RollingUpdate` | -| `converter.updateStrategy.rollingUpdate.maxUnavailable` | Maximum number of Converter Pods unavailable during the update process. Used only when `converter.updateStrategy.type=RollingUpdate` | `25%` | -| `converter.updateStrategy.rollingUpdate.maxSurge` | Maximum number of Converter Pods created over the desired number of Pods. Used only when `converter.updateStrategy.type=RollingUpdate` | `25%` | +| `converter.updateStrategy.type` | Converter deployment update strategy type | `Recreate` | | `converter.customPodAntiAffinity` | Prohibiting the scheduling of Converter Pods relative to other Pods containing the specified labels on the same node | `{}` | | `converter.podAffinity` | Defines [Pod affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity) rules for Converter Pods scheduling by nodes relative to other Pods | `{}` | | `converter.nodeAffinity` | Defines [Node affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity) rules for Converter Pods scheduling by nodes | `{}` | diff --git a/values.yaml b/values.yaml index 65e8beeb3..3d101fa6b 100644 --- a/values.yaml +++ b/values.yaml @@ -752,13 +752,7 @@ converter: ## Update strategy used to replace old Pods by new ones. Allowed values: `RollingUpdate` or `Recreate` ## converter.updateStrategy.type Docservice deployment update strategy type updateStrategy: - type: RollingUpdate - ## converter.updateStrategy.rollingUpdate Used only when `converter.updateStrategy.type=RollingUpdate` - rollingUpdate: - ## converter.updateStrategy.rollingUpdate.maxUnavailable Maximum number of Converter Pods unavailable during the update process - maxUnavailable: 25% - ## converter.updateStrategy.rollingUpdate.maxSurge Maximum number of Converter Pods created over the desired number of Pods - maxSurge: 25% + type: Recreate ## converter.customPodAntiAffinity Prohibiting the scheduling of Converter Pods relative to other Pods containing the specified labels on the same node ## Example: ## customPodAntiAffinity: