mirror of
https://github.com/bitnami/charts.git
synced 2026-08-10 14:15:55 +08:00
[bitnami/minio] Add updateStrategy parameter for deployment mode
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
apiVersion: v1
|
||||
version: 2.0.1
|
||||
version: 2.1.0
|
||||
appVersion: 2019.10.2
|
||||
description: MinIO is an object storage server, compatible with Amazon S3 cloud storage service, mainly used for storing unstructured data (such as photos, videos, log files, etc.)
|
||||
keywords:
|
||||
|
||||
+12
-1
@@ -71,13 +71,14 @@ The following table lists the configurable parameters of the MinIO chart and the
|
||||
| `volumePermissions.enabled` | Enable init container that changes volume permissions in the data directory (for cases where the default k8s `runAsUser` and `fsUser` values do not work) | `false` |
|
||||
| `volumePermissions.image.registry` | Init container volume-permissions image registry | `docker.io` |
|
||||
| `volumePermissions.image.repository` | Init container volume-permissions image name | `bitnami/minideb` |
|
||||
| `volumePermissions.image.tag` | Init container volume-permissions image tag | `stretch` |
|
||||
| `volumePermissions.image.tag` | Init container volume-permissions image tag | `stretch` |
|
||||
| `volumePermissions.image.pullPolicy` | Init container volume-permissions image pull policy | `Always` |
|
||||
| `volumePermissions.resources` | Init container resource requests/limit | `nil` |
|
||||
| `mode` | MinIO server mode (`standalone` or `distributed`) | `standalone` |
|
||||
| `statefulset.replicaCount` | Number of pods (only for Minio distributed mode). Should be 4 <= x <= 32 | `4` |
|
||||
| `statefulset.updateStrategy` | Statefulset update strategy policy | `RollingUpdate` |
|
||||
| `statefulset.podManagementpolicy` | Statefulset pods management policy | `Parallel` |
|
||||
| `deployment.updateStrategy` | Deployment update strategy policy | `Recreate` |
|
||||
| `existingSecret` | Existing secret with MinIO credentials | `nil` |
|
||||
| `useCredentialsFile` | Have the secret mounted as a file instead of env vars | `false` |
|
||||
| `accessKey.password` | MinIO Access Key. Ignored if existing secret is provided. | _random 10 character alphanumeric string_ |
|
||||
@@ -205,6 +206,16 @@ This chart includes a `values-production.yaml` file where you can find some para
|
||||
+ networkPolicy.allowExternal: false
|
||||
```
|
||||
|
||||
- Set deployment updateStrategy to RollingUpdate:
|
||||
```diff
|
||||
- deployment:
|
||||
- updateStrategy:
|
||||
- type: Recreate
|
||||
+ deployment:
|
||||
+ updateStrategy:
|
||||
+ type: RollingUpdate
|
||||
```
|
||||
|
||||
### Distributed mode
|
||||
|
||||
You can start the MinIO chart in distributed mode with the following parameter: `mode=distributed`
|
||||
|
||||
@@ -9,6 +9,9 @@ metadata:
|
||||
app.kubernetes.io/instance: {{ .Release.Name }}
|
||||
app.kubernetes.io/managed-by: {{ .Release.Service }}
|
||||
spec:
|
||||
{{- if .Values.deployment.updateStrategy }}
|
||||
strategy: {{ toYaml .Values.deployment.updateStrategy | nindent 4 }}
|
||||
{{- end }}
|
||||
selector:
|
||||
matchLabels:
|
||||
app.kubernetes.io/name: {{ include "minio.name" . }}
|
||||
|
||||
@@ -76,6 +76,18 @@ volumePermissions:
|
||||
##
|
||||
mode: distributed
|
||||
|
||||
deployment:
|
||||
## Set to Recreate if you use persistent volume that cannot be mounted by more than one pods to makesure the pods is destroyed first.
|
||||
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy
|
||||
## Example:
|
||||
## updateStrategy:
|
||||
## type: RollingUpdate
|
||||
## rollingUpdate:
|
||||
## maxSurge: 25%
|
||||
## maxUnavailable: 25%
|
||||
updateStrategy:
|
||||
type: RollingUpdate
|
||||
|
||||
statefulset:
|
||||
## Update strategy, can be set to RollingUpdate or OnDelete by default.
|
||||
## ref: https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets
|
||||
@@ -274,7 +286,7 @@ ingress:
|
||||
hosts:
|
||||
- name: minio.local
|
||||
path: /
|
||||
|
||||
|
||||
## Set this to true in order to enable TLS on the ingress record
|
||||
tls: false
|
||||
|
||||
|
||||
@@ -76,6 +76,18 @@ volumePermissions:
|
||||
##
|
||||
mode: standalone
|
||||
|
||||
deployment:
|
||||
## Set to Recreate if you use persistent volume that cannot be mounted by more than one pods to makesure the pods is destroyed first.
|
||||
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#strategy
|
||||
## Example:
|
||||
## updateStrategy:
|
||||
## type: RollingUpdate
|
||||
## rollingUpdate:
|
||||
## maxSurge: 25%
|
||||
## maxUnavailable: 25%
|
||||
updateStrategy:
|
||||
type: Recreate
|
||||
|
||||
statefulset:
|
||||
## Update strategy, can be set to RollingUpdate or OnDelete by default.
|
||||
## ref: https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets
|
||||
|
||||
Reference in New Issue
Block a user