Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the upgrade strategy for converter #319

Merged
merged 2 commits into from
Jul 15, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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
4 changes: 1 addition & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 | `{}` |
Expand Down
8 changes: 1 addition & 7 deletions values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
Loading