Skip to content

Commit

Permalink
[stable/minio] update default values (helm#22805)
Browse files Browse the repository at this point in the history 
Signed-off-by: Harshavardhana <harsha@minio.io>
  • Loading branch information
@harshavardhana
harshavardhana authored Jun 15, 2020
1 parent 4d16b9b commit bd8e234
Show file tree
Hide file tree
Showing 3 changed files with 33 additions and 24 deletions.
2 changes: 1 addition & 1 deletion stable/minio/Chart.yaml
View file
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
apiVersion: v1
description: MinIO is a high performance data infrastructure for machine learning, analytics and application data workloads.
name: minio
version: 5.0.28
version: 5.0.29
appVersion: master
keywords:
- storage
Expand Down
32 changes: 20 additions & 12 deletions stable/minio/README.md
View file
Original file line number Diff line number Diff line change
@@ -1,10 +1,12 @@
MinIO
=====

[MinIO](https://min.io) is a distributed object storage service for high performance, high scale data infrastructures. It is a drop in replacement for AWS S3 in your own environment. It uses erasure coding to provide highly resilient storage that can tolerate failures of upto n/2 nodes. It runs on cloud, container, kubernetes and bare-metal environments. It is simple enough to be deployed in seconds, and can scale to 100s of peta bytes. MinIO is suitable for storing objects such as photos, videos, log files, backups, VM and container images.
[MinIO](https://min.io) is a High Performance Object Storage released under Apache License v2.0. It is API compatible with Amazon S3 cloud storage service. Use MinIO to build high performance infrastructure for machine learning, analytics and application data workloads.

MinIO supports [distributed mode](https://docs.minio.io/docs/distributed-minio-quickstart-guide). In distributed mode, you can pool multiple drives (even on different machines) into a single object storage server.

For more detailed documentation please visit [here](https://docs.minio.io/)

Introduction
------------

Expand Down Expand Up @@ -66,6 +68,12 @@ Assuming your release is named as `my-release`, delete it using the command:
$ helm delete my-release
```

or

```bash
$ helm uninstall my-release
```

The command removes all the Kubernetes components associated with the chart and deletes the release.

Upgrading the Chart
Expand Down Expand Up @@ -95,10 +103,10 @@ The following table lists the configurable parameters of the MinIO chart and the
| `nameOverride` | Provide a name in place of `minio` | `""` |
| `fullnameOverride` | Provide a name to substitute for the full names of resources | `""` |
| `image.repository` | Image repository | `minio/minio` |
| `image.tag` | MinIO image tag. Possible values listed [here](https://hub.docker.com/r/minio/minio/tags/). | `RELEASE.2020-04-28T23-56-56Z` |
| `image.tag` | MinIO image tag. Possible values listed [here](https://hub.docker.com/r/minio/minio/tags/). | `RELEASE.2020-06-14T18-32-17Z` |
| `image.pullPolicy` | Image pull policy | `IfNotPresent` |
| `mcImage.repository` | Client image repository | `minio/mc` |
| `mcImage.tag` | mc image tag. Possible values listed [here](https://hub.docker.com/r/minio/mc/tags/). | `RELEASE.2020-04-25T00-43-23Z` |
| `mcImage.tag` | mc image tag. Possible values listed [here](https://hub.docker.com/r/minio/mc/tags/). | `RELEASE.2020-05-28T23-43-36Z` |
| `mcImage.pullPolicy` | mc Image pull policy | `IfNotPresent` |
| `ingress.enabled` | Enables Ingress | `false` |
| `ingress.labels ` | Ingress labels | `{}` |
Expand All @@ -125,12 +133,12 @@ The following table lists the configurable parameters of the MinIO chart and the
| `serviceAccount.create` | Toggle creation of new service account | `true` |
| `serviceAccount.name` | Name of service account to create and/or use | `""` |
| `persistence.enabled` | Use persistent volume to store data | `true` |
| `persistence.size` | Size of persistent volume claim | `10Gi` |
| `persistence.size` | Size of persistent volume claim | `500Gi` |
| `persistence.existingClaim` | Use an existing PVC to persist data | `nil` |
| `persistence.storageClass` | Storage class name of PVC | `nil` |
| `persistence.accessMode` | ReadWriteOnce or ReadOnly | `ReadWriteOnce` |
| `persistence.subPath` | Mount a sub directory of the persistent volume if set | `""` |
| `resources` | CPU/Memory resource requests/limits | Memory: `256Mi`, CPU: `100m` |
| `resources` | Memory resource requests | Memory: `4Gi` |
| `priorityClassName` | Pod priority settings | `""` |
| `securityContext.enabled` | Enable to run containers as non-root. NOTE: if `persistence.enabled=false` then securityContext will be automatically disabled | `true` |
| `securityContext.runAsUser` | User id of the user for the container | `1000` |
Expand All @@ -144,13 +152,13 @@ The following table lists the configurable parameters of the MinIO chart and the
| `tls.enabled` | Enable TLS for MinIO server | `false` |
| `tls.certSecret` | Kubernetes Secret with `public.crt` and `private.key` files. | `""` |
| `livenessProbe.initialDelaySeconds` | Delay before liveness probe is initiated | `5` |
| `livenessProbe.periodSeconds` | How often to perform the probe | `30` |
| `livenessProbe.periodSeconds` | How often to perform the probe | `5` |
| `livenessProbe.timeoutSeconds` | When the probe times out | `1` |
| `livenessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated | `5` |
| `readinessProbe.periodSeconds` | How often to perform the probe | `15` |
| `readinessProbe.timeoutSeconds` | When the probe times out | `1` |
| `livenessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `1` |
| `readinessProbe.initialDelaySeconds` | Delay before readiness probe is initiated | `60` |
| `readinessProbe.periodSeconds` | How often to perform the probe | `5` |
| `readinessProbe.timeoutSeconds` | When the probe times out (should be 1s higher than your `MINIO_API_READY_DEADLINE` timeout | `6` |
| `readinessProbe.successThreshold` | Minimum consecutive successes for the probe to be considered successful after having failed. | `1` |
| `readinessProbe.failureThreshold` | Minimum consecutive failures for the probe to be considered failed after having succeeded. | `3` |
| `defaultBucket.enabled` | If set to true, a bucket will be created after MinIO install | `false` |
Expand All @@ -176,7 +184,7 @@ The following table lists the configurable parameters of the MinIO chart and the
| `nasgateway.replicas` | Number of NAS gateway instances to be run in parallel on a PV | `4` |
| `b2gateway.enabled` | Use MinIO as a [Backblaze B2 gateway](https://github.com/minio/minio/blob/master/docs/gateway/b2.md) | `false` |
| `b2gateway.replicas` | Number of b2 gateway instances to run in parallel | `4` |
| `environment` | Set MinIO server relevant environment variables in `values.yaml` file. MinIO containers will be passed these variables when they start. | `MINIO_BROWSER: "on"` |
| `environment` | Set MinIO server relevant environment variables in `values.yaml` file. MinIO containers will be passed these variables when they start. | `MINIO_API_READY_DEADLINE: "5s"` |
| `metrics.serviceMonitor.enabled` | Set this to `true` to create ServiceMonitor for Prometheus operator | `false` |
| `metrics.serviceMonitor.additionalLabels` | Additional labels that can be used so ServiceMonitor will be discovered by Prometheus | `{}` |
| `metrics.serviceMonitor.namespace` | Optional namespace in which to create ServiceMonitor | `nil` |
Expand All @@ -194,7 +202,7 @@ You can specify each parameter using the `--set key=value[,key=value]` argument

```bash
$ helm install --name my-release \
--set persistence.size=100Gi \
--set persistence.size=1Ti \
stable/minio
```

Expand Down
23 changes: 12 additions & 11 deletions stable/minio/values.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,15 @@ clusterDomain: cluster.local
##
image:
repository: minio/minio
tag: RELEASE.2020-04-28T23-56-56Z
tag: RELEASE.2020-06-14T18-32-17Z
pullPolicy: IfNotPresent

## Set default image, imageTag, and imagePullPolicy for the `mc` (the minio
## client used to create a default bucket).
##
mcImage:
repository: minio/mc
tag: RELEASE.2020-04-25T00-43-23Z
tag: RELEASE.2020-05-28T23-43-36Z
pullPolicy: IfNotPresent

## Set default image, imageTag, and imagePullPolicy for the `jq` (the JSON
Expand Down Expand Up @@ -111,7 +111,7 @@ persistence:
storageClass: ""
VolumeName: ""
accessMode: ReadWriteOnce
size: 10Gi
size: 500Gi

## If subPath is set mount a sub folder of a volume instead of the root of the volume.
## This is especially handy for volume plugins that don't natively support sub mounting (like glusterfs).
Expand All @@ -127,7 +127,7 @@ service:
type: ClusterIP
clusterIP: ~
port: 9000
nodePort: 31311
nodePort: 32000

## List of IP addresses at which the Prometheus server service is available
## Ref: https://kubernetes.io/docs/user-guide/services/#external-ips
Expand Down Expand Up @@ -189,14 +189,15 @@ podLabels: {}
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/
livenessProbe:
initialDelaySeconds: 5
periodSeconds: 30
periodSeconds: 5
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 3
failureThreshold: 1
readinessProbe:
initialDelaySeconds: 60
periodSeconds: 15
timeoutSeconds: 1
initialDelaySeconds: 30
periodSeconds: 5
## Set this to 1s higher than MINIO_API_READY_DEADLINE
timeoutSeconds: 6
successThreshold: 1
failureThreshold: 3

Expand All @@ -205,8 +206,7 @@ readinessProbe:
##
resources:
requests:
memory: 256Mi
cpu: 250m
memory: 4Gi

## Create a bucket after minio install
##
Expand Down Expand Up @@ -291,6 +291,7 @@ b2gateway:
## Use this field to add environment variables relevant to Minio server. These fields will be passed on to Minio container(s)
## when Chart is deployed
environment:
MINIO_API_READY_DEADLINE: "5s"
## Please refer for comprehensive list https://docs.minio.io/docs/minio-server-configuration-guide.html

networkPolicy:
Expand Down

0 comments on commit bd8e234

Please sign in to comment.