mirror of
https://github.com/bitnami/charts.git
synced 2026-03-14 06:47:28 +08:00
bb0988ae3d
* minio add prometheus rule Signed-off-by: lusson <lusson@foxmail.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <containers@bitnami.com> * update code style Signed-off-by: lusson <lusson@foxmail.com> * Update README.md with readme-generator-for-helm Signed-off-by: Bitnami Containers <containers@bitnami.com> Co-authored-by: Bitnami Containers <containers@bitnami.com>
1108 lines
45 KiB
YAML
1108 lines
45 KiB
YAML
## @section Global parameters
|
||
## Global Docker image parameters
|
||
## Please, note that this will override the image parameters, including dependencies, configured to use the global value
|
||
## Current available global Docker image parameters: imageRegistry, imagePullSecrets and storageClass
|
||
|
||
## @param global.imageRegistry Global Docker image registry
|
||
## @param global.imagePullSecrets Global Docker registry secret names as an array
|
||
## @param global.storageClass Global StorageClass for Persistent Volume(s)
|
||
##
|
||
global:
|
||
imageRegistry: ""
|
||
## e.g.
|
||
## imagePullSecrets:
|
||
## - myRegistryKeySecretName
|
||
##
|
||
imagePullSecrets: []
|
||
storageClass: ""
|
||
|
||
## @section Common parameters
|
||
|
||
## @param nameOverride String to partially override common.names.fullname template (will maintain the release name)
|
||
##
|
||
nameOverride: ""
|
||
## @param fullnameOverride String to fully override common.names.fullname template
|
||
##
|
||
fullnameOverride: ""
|
||
## @param commonLabels Labels to add to all deployed objects
|
||
##
|
||
commonLabels: {}
|
||
## @param commonAnnotations Annotations to add to all deployed objects
|
||
##
|
||
commonAnnotations: {}
|
||
## @param kubeVersion Force target Kubernetes version (using Helm capabilities if not set)
|
||
##
|
||
kubeVersion: ""
|
||
## @param clusterDomain Default Kubernetes cluster domain
|
||
##
|
||
clusterDomain: cluster.local
|
||
## @param extraDeploy Array of extra objects to deploy with the release
|
||
##
|
||
extraDeploy: []
|
||
|
||
## @section MinIO® parameters
|
||
|
||
## Bitnami MinIO® image version
|
||
## ref: https://hub.docker.com/r/bitnami/minio/tags/
|
||
## @param image.registry MinIO® image registry
|
||
## @param image.repository MinIO® image repository
|
||
## @param image.tag MinIO® image tag (immutable tags are recommended)
|
||
## @param image.pullPolicy Image pull policy
|
||
## @param image.pullSecrets Specify docker-registry secret names as an array
|
||
## @param image.debug Specify if debug logs should be enabled
|
||
##
|
||
image:
|
||
registry: docker.io
|
||
repository: bitnami/minio
|
||
tag: 2022.5.23-debian-10-r0
|
||
## Specify a imagePullPolicy
|
||
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
|
||
## ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images
|
||
##
|
||
pullPolicy: IfNotPresent
|
||
## Optionally specify an array of imagePullSecrets.
|
||
## Secrets must be manually created in the namespace.
|
||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
|
||
## e.g:
|
||
## pullSecrets:
|
||
## - myRegistryKeySecretName
|
||
##
|
||
pullSecrets: []
|
||
## Set to true if you would like to see extra information on logs
|
||
##
|
||
debug: false
|
||
## Bitnami MinIO® Client image version
|
||
## ref: https://hub.docker.com/r/bitnami/minio-client/tags/
|
||
## @param clientImage.registry MinIO® Client image registry
|
||
## @param clientImage.repository MinIO® Client image repository
|
||
## @param clientImage.tag MinIO® Client image tag (immutable tags are recommended)
|
||
##
|
||
clientImage:
|
||
registry: docker.io
|
||
repository: bitnami/minio-client
|
||
tag: 2022.5.9-debian-10-r13
|
||
## @param mode MinIO® server mode (`standalone` or `distributed`)
|
||
## ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide
|
||
##
|
||
mode: standalone
|
||
## MinIO® authentication parameters
|
||
##
|
||
auth:
|
||
## @param auth.rootUser MinIO® root username
|
||
##
|
||
rootUser: admin
|
||
## @param auth.rootPassword Password for MinIO® root user
|
||
##
|
||
rootPassword: ""
|
||
## @param auth.existingSecret Use existing secret for credentials details (`auth.rootUser` and `auth.rootPassword` will be ignored and picked up from this secret). The secret has to contain the keys `root-user` and `root-password`)
|
||
##
|
||
existingSecret: ""
|
||
## @param auth.forcePassword Force users to specify required passwords
|
||
##
|
||
forcePassword: false
|
||
## @param auth.useCredentialsFiles Mount credentials as a files instead of using an environment variable
|
||
##
|
||
useCredentialsFiles: false
|
||
## @param auth.forceNewKeys Force root credentials (user and password) to be reconfigured every time they change in the secrets
|
||
##
|
||
forceNewKeys: false
|
||
## @param defaultBuckets Comma, semi-colon or space separated list of buckets to create at initialization (only in standalone mode)
|
||
## e.g:
|
||
## defaultBuckets: "my-bucket, my-second-bucket"
|
||
##
|
||
defaultBuckets: ""
|
||
## @param disableWebUI Disable MinIO® Web UI
|
||
## ref: https://github.com/minio/minio/tree/master/docs/config/#browser
|
||
##
|
||
disableWebUI: false
|
||
## Enable tls in front of MinIO® containers.
|
||
##
|
||
tls:
|
||
## @param tls.enabled Enable tls in front of the container
|
||
##
|
||
enabled: false
|
||
## @param tls.existingSecret Name of an existing secret holding the certificate information
|
||
##
|
||
existingSecret: ""
|
||
## @param tls.mountPath The mount path where the secret will be located
|
||
## Custom mount path where the certificates will be located, if empty will default to /certs
|
||
mountPath: ""
|
||
## @param extraEnvVars Extra environment variables to be set on MinIO® container
|
||
## e.g:
|
||
## extraEnvVars:
|
||
## - name: FOO
|
||
## value: "bar"
|
||
##
|
||
extraEnvVars: {}
|
||
## @param extraEnvVarsCM ConfigMap with extra environment variables
|
||
##
|
||
extraEnvVarsCM: ""
|
||
## @param extraEnvVarsSecret Secret with extra environment variables
|
||
##
|
||
extraEnvVarsSecret: ""
|
||
## @param command Default container command (useful when using custom images). Use array form
|
||
##
|
||
command: []
|
||
## @param args Default container args (useful when using custom images). Use array form
|
||
##
|
||
args: []
|
||
|
||
## @section MinIO® deployment/statefulset parameters
|
||
|
||
## @param schedulerName Specifies the schedulerName, if it's nil uses kube-scheduler
|
||
## https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
|
||
##
|
||
schedulerName: ""
|
||
## MinIO® deployment parameters
|
||
## Only when 'mode' is 'standalone' or 'gateway.enabled' is 'true'
|
||
##
|
||
deployment:
|
||
## @param deployment.updateStrategy.type Deployment strategy type
|
||
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies
|
||
## e.g:
|
||
## updateStrategy:
|
||
## type: RollingUpdate
|
||
## rollingUpdate:
|
||
## maxSurge: 25%
|
||
## maxUnavailable: 25%
|
||
##
|
||
updateStrategy:
|
||
type: Recreate
|
||
## MinIO® statefulset parameters
|
||
## Only when mode is 'distributed'
|
||
##
|
||
statefulset:
|
||
## @param statefulset.updateStrategy.type StatefulSet strategy type
|
||
## ref: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies
|
||
## e.g:
|
||
## updateStrategy:
|
||
## type: RollingUpdate
|
||
## rollingUpdate:
|
||
## maxSurge: 25%
|
||
## maxUnavailable: 25%
|
||
##
|
||
updateStrategy:
|
||
type: RollingUpdate
|
||
## @param statefulset.podManagementPolicy StatefulSet controller supports relax its ordering guarantees while preserving its uniqueness and identity guarantees. There are two valid pod management policies: OrderedReady and Parallel
|
||
## ref: https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#pod-management-policy
|
||
##
|
||
podManagementPolicy: Parallel
|
||
## @param statefulset.replicaCount Number of pods per zone (only for MinIO® distributed mode). Should be even and `>= 4`
|
||
##
|
||
replicaCount: 4
|
||
## @param statefulset.zones Number of zones (only for MinIO® distributed mode)
|
||
##
|
||
zones: 1
|
||
## @param statefulset.drivesPerNode Number of drives attached to every node (only for MinIO® distributed mode)
|
||
##
|
||
drivesPerNode: 1
|
||
|
||
## MinIO® provisioning
|
||
##
|
||
provisioning:
|
||
## @param provisioning.enabled Enable MinIO® provisioning Job
|
||
##
|
||
enabled: false
|
||
## @param provisioning.schedulerName Name of the k8s scheduler (other than default) for MinIO® provisioning
|
||
## ref: https://kubernetes.io/docs/tasks/administer-cluster/configure-multiple-schedulers/
|
||
##
|
||
schedulerName: ""
|
||
## @param provisioning.podAnnotations Provisioning Pod annotations.
|
||
##
|
||
podAnnotations: {}
|
||
## @param provisioning.command Default provisioning container command (useful when using custom images). Use array form
|
||
##
|
||
command: []
|
||
## @param provisioning.args Default provisioning container args (useful when using custom images). Use array form
|
||
##
|
||
args: []
|
||
## @param provisioning.extraVolumes Optionally specify extra list of additional volumes for MinIO® provisioning pod
|
||
##
|
||
extraVolumes: []
|
||
## @param provisioning.extraVolumeMounts Optionally specify extra list of additional volumeMounts for MinIO® provisioning container
|
||
##
|
||
extraVolumeMounts: []
|
||
## We usually recommend not to specify default resources and to leave this as a conscious
|
||
## choice for the user. This also increases chances charts run on environments with little
|
||
## resources, such as Minikube. If you do want to specify resources, uncomment the following
|
||
## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
|
||
## @param provisioning.resources.limits The resources limits for the container
|
||
## @param provisioning.resources.requests The requested resources for the container
|
||
##
|
||
resources:
|
||
## Example:
|
||
## limits:
|
||
## cpu: 100m
|
||
## memory: 64Mi
|
||
limits: {}
|
||
## Examples:
|
||
## requests:
|
||
## cpu: 200m
|
||
## memory: 128Mi
|
||
requests: {}
|
||
## @param provisioning.policies MinIO® policies provisioning
|
||
## https://docs.min.io/docs/minio-admin-complete-guide.html#policy
|
||
## e.g.
|
||
## policies:
|
||
## - name: custom-bucket-specific-policy
|
||
## statements:
|
||
## - resources:
|
||
## - "arn:aws:s3:::my-bucket"
|
||
## actions:
|
||
## - "s3:GetBucketLocation"
|
||
## - "s3:ListBucket"
|
||
## - "s3:ListBucketMultipartUploads"
|
||
## - resources:
|
||
## - "arn:aws:s3:::my-bucket/*"
|
||
## # Allowed values: "Allow" | "Deny"
|
||
## # Defaults to "Deny" if not specified
|
||
## effect: "Allow"
|
||
## actions:
|
||
## - "s3:AbortMultipartUpload"
|
||
## - "s3:DeleteObject"
|
||
## - "s3:GetObject"
|
||
## - "s3:ListMultipartUploadParts"
|
||
## - "s3:PutObject"
|
||
policies: []
|
||
## @param provisioning.users MinIO® users provisioning. Can be used in addition to provisioning.usersExistingSecrets.
|
||
## https://docs.min.io/docs/minio-admin-complete-guide.html#user
|
||
## e.g.
|
||
## users:
|
||
## - username: test-username
|
||
## password: test-password
|
||
## disabled: false
|
||
## policies:
|
||
## - readwrite
|
||
## - consoleAdmin
|
||
## - diagnostics
|
||
## # When set to true, it will replace all policies with the specified.
|
||
## # When false, the policies will be added to the existing.
|
||
## setPolicies: false
|
||
users: []
|
||
## @param provisioning.usersExistingSecrets Array if existing secrets containing MinIO® users to be provisioned. Can be used in addition to provisioning.users.
|
||
## https://docs.min.io/docs/minio-admin-complete-guide.html#user
|
||
##
|
||
## Instead of configuring users inside values.yaml, referring to existing Kubernetes secrets containing user
|
||
## configurations is possible.
|
||
## e.g.
|
||
## usersExistingSecrets:
|
||
## - centralized-minio-users
|
||
##
|
||
## All provided Kubernetes secrets require a specific data structure. The same data from the provisioning.users example above
|
||
## can be defined via secrets with the following data structure. The secret keys have no meaning to the provisioning job except that
|
||
## they are used as filenames.
|
||
## ## apiVersion: v1
|
||
## ## kind: Secret
|
||
## ## metadata:
|
||
## ## name: centralized-minio-users
|
||
## ## type: Opaque
|
||
## ## stringData:
|
||
## ## username1: |
|
||
## ## username=test-username
|
||
## ## password=test-password
|
||
## ## disabled=false
|
||
## ## policies=readwrite,consoleAdmin,diagnostics
|
||
## ## setPolicies=false
|
||
usersExistingSecrets: []
|
||
## @param provisioning.groups MinIO® groups provisioning
|
||
## https://docs.min.io/docs/minio-admin-complete-guide.html#group
|
||
## e.g.
|
||
## groups
|
||
## - name: test-group
|
||
## disabled: false
|
||
## members:
|
||
## - test-username
|
||
## policies:
|
||
## - readwrite
|
||
## # When set to true, it will replace all policies with the specified.
|
||
## # When false, the policies will be added to the existing.
|
||
## setPolicies: false
|
||
groups: []
|
||
## @param provisioning.buckets MinIO® buckets, versioning, lifecycle, quota and tags provisioning
|
||
## Buckets https://docs.min.io/docs/minio-client-complete-guide.html#mb
|
||
## Lifecycle https://docs.min.io/docs/minio-client-complete-guide.html#ilm
|
||
## Quotas https://docs.min.io/docs/minio-admin-complete-guide.html#bucket
|
||
## Tags https://docs.min.io/docs/minio-client-complete-guide.html#tag
|
||
## Versioning https://docs.min.io/docs/minio-client-complete-guide.html#version
|
||
## e.g.
|
||
## buckets:
|
||
## - name: test-bucket
|
||
## region: us-east-1
|
||
## # Only when mode is 'distributed'
|
||
## # ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide
|
||
## versioning: false
|
||
## # Versioning is automatically enabled if withLock is true
|
||
## # ref: https://docs.min.io/docs/minio-bucket-versioning-guide.html
|
||
## withLock: true
|
||
## # Only when mode is 'distributed'
|
||
## # ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide
|
||
## lifecycle:
|
||
## - id: TestPrefix7dRetention
|
||
## prefix: test-prefix
|
||
## disabled: false
|
||
## expiry:
|
||
## days: 7
|
||
## # Days !OR! date
|
||
## # date: "2021-11-11T00:00:00Z"
|
||
## nonconcurrentDays: 3
|
||
## # Only when mode is 'distributed'
|
||
## # ref: https://docs.minio.io/docs/distributed-minio-quickstart-guide
|
||
## quota:
|
||
## # hard or clear(+ omit size)
|
||
## type: hard
|
||
## size: 10GiB
|
||
## tags:
|
||
## key1: value1
|
||
buckets: []
|
||
## @param provisioning.config MinIO® config provisioning
|
||
## https://docs.min.io/docs/minio-server-configuration-guide.html
|
||
## e.g.
|
||
## config:
|
||
## - name: region
|
||
## options:
|
||
## name: us-east-1
|
||
config: []
|
||
|
||
## @param hostAliases MinIO® pod host aliases
|
||
## https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/
|
||
##
|
||
hostAliases: []
|
||
## @param containerPorts.api MinIO® container port to open for MinIO® API
|
||
## @param containerPorts.console MinIO® container port to open for MinIO® Console
|
||
##
|
||
containerPorts:
|
||
api: 9000
|
||
console: 9001
|
||
## MinIO® pod Security Context
|
||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-pod
|
||
## @param podSecurityContext.enabled Enable pod Security Context
|
||
## @param podSecurityContext.fsGroup Group ID for the container
|
||
##
|
||
podSecurityContext:
|
||
enabled: true
|
||
fsGroup: 1001
|
||
## MinIO® container Security Context
|
||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-the-security-context-for-a-container
|
||
## @param containerSecurityContext.enabled Enable container Security Context
|
||
## @param containerSecurityContext.runAsUser User ID for the container
|
||
## @param containerSecurityContext.runAsNonRoot Avoid running as root User
|
||
##
|
||
containerSecurityContext:
|
||
enabled: true
|
||
runAsUser: 1001
|
||
runAsNonRoot: true
|
||
## @param podLabels Extra labels for MinIO® pods
|
||
## Ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
|
||
##
|
||
podLabels: {}
|
||
## @param podAnnotations Annotations for MinIO® pods
|
||
## ref: https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/
|
||
##
|
||
podAnnotations: {}
|
||
## @param podAffinityPreset Pod affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard`
|
||
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
|
||
##
|
||
podAffinityPreset: ""
|
||
## @param podAntiAffinityPreset Pod anti-affinity preset. Ignored if `affinity` is set. Allowed values: `soft` or `hard`
|
||
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity
|
||
##
|
||
podAntiAffinityPreset: soft
|
||
## Node affinity preset
|
||
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity
|
||
##
|
||
nodeAffinityPreset:
|
||
## @param nodeAffinityPreset.type Node affinity preset type. Ignored if `affinity` is set. Allowed values: `soft` or `hard`
|
||
##
|
||
type: ""
|
||
## @param nodeAffinityPreset.key Node label key to match. Ignored if `affinity` is set.
|
||
## E.g.
|
||
## key: "kubernetes.io/e2e-az-name"
|
||
##
|
||
key: ""
|
||
## @param nodeAffinityPreset.values Node label values to match. Ignored if `affinity` is set.
|
||
## E.g.
|
||
## values:
|
||
## - e2e-az1
|
||
## - e2e-az2
|
||
##
|
||
values: []
|
||
## @param affinity Affinity for pod assignment. Evaluated as a template.
|
||
## ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
|
||
## Note: podAffinityPreset, podAntiAffinityPreset, and nodeAffinityPreset will be ignored when it's set
|
||
##
|
||
affinity: {}
|
||
## @param nodeSelector Node labels for pod assignment. Evaluated as a template.
|
||
## ref: https://kubernetes.io/docs/user-guide/node-selection/
|
||
##
|
||
nodeSelector: {}
|
||
## @param tolerations Tolerations for pod assignment. Evaluated as a template.
|
||
## ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
|
||
##
|
||
tolerations: []
|
||
## @param topologySpreadConstraints Topology Spread Constraints for MinIO® pods assignment spread across your cluster among failure-domains
|
||
## Ref: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/#spread-constraints-for-pods
|
||
##
|
||
topologySpreadConstraints: []
|
||
## @param priorityClassName MinIO® pods' priorityClassName
|
||
##
|
||
priorityClassName: ""
|
||
## MinIO® containers' resource requests and limits
|
||
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
|
||
## We usually recommend not to specify default resources and to leave this as a conscious
|
||
## choice for the user. This also increases chances charts run on environments with little
|
||
## resources, such as Minikube. If you do want to specify resources, uncomment the following
|
||
## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
|
||
## @param resources.limits The resources limits for the MinIO® container
|
||
## @param resources.requests The requested resources for the MinIO® container
|
||
##
|
||
resources:
|
||
## Example:
|
||
## limits:
|
||
## cpu: 250m
|
||
## memory: 256Mi
|
||
limits: {}
|
||
## Examples:
|
||
## requests:
|
||
## cpu: 250m
|
||
## memory: 256Mi
|
||
requests: {}
|
||
## Configure extra options for liveness probe
|
||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
|
||
## @param livenessProbe.enabled Enable livenessProbe
|
||
## @param livenessProbe.initialDelaySeconds Initial delay seconds for livenessProbe
|
||
## @param livenessProbe.periodSeconds Period seconds for livenessProbe
|
||
## @param livenessProbe.timeoutSeconds Timeout seconds for livenessProbe
|
||
## @param livenessProbe.failureThreshold Failure threshold for livenessProbe
|
||
## @param livenessProbe.successThreshold Success threshold for livenessProbe
|
||
##
|
||
livenessProbe:
|
||
enabled: true
|
||
initialDelaySeconds: 5
|
||
periodSeconds: 5
|
||
timeoutSeconds: 5
|
||
successThreshold: 1
|
||
failureThreshold: 5
|
||
## Configure extra options for readiness probe
|
||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
|
||
## @param readinessProbe.enabled Enable readinessProbe
|
||
## @param readinessProbe.initialDelaySeconds Initial delay seconds for readinessProbe
|
||
## @param readinessProbe.periodSeconds Period seconds for readinessProbe
|
||
## @param readinessProbe.timeoutSeconds Timeout seconds for readinessProbe
|
||
## @param readinessProbe.failureThreshold Failure threshold for readinessProbe
|
||
## @param readinessProbe.successThreshold Success threshold for readinessProbe
|
||
##
|
||
readinessProbe:
|
||
enabled: true
|
||
initialDelaySeconds: 5
|
||
periodSeconds: 5
|
||
timeoutSeconds: 1
|
||
successThreshold: 1
|
||
failureThreshold: 5
|
||
## Configure extra options for startupProbe probe
|
||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#configure-probes
|
||
## @param startupProbe.enabled Enable startupProbe
|
||
## @param startupProbe.initialDelaySeconds Initial delay seconds for startupProbe
|
||
## @param startupProbe.periodSeconds Period seconds for startupProbe
|
||
## @param startupProbe.timeoutSeconds Timeout seconds for startupProbe
|
||
## @param startupProbe.failureThreshold Failure threshold for startupProbe
|
||
## @param startupProbe.successThreshold Success threshold for startupProbe
|
||
##
|
||
startupProbe:
|
||
enabled: false
|
||
initialDelaySeconds: 0
|
||
periodSeconds: 10
|
||
timeoutSeconds: 5
|
||
successThreshold: 1
|
||
failureThreshold: 60
|
||
## @param customLivenessProbe Override default liveness probe
|
||
##
|
||
customLivenessProbe: {}
|
||
## @param customReadinessProbe Override default readiness probe
|
||
##
|
||
customReadinessProbe: {}
|
||
## @param customStartupProbe Override default startup probe
|
||
##
|
||
customStartupProbe: {}
|
||
## @param lifecycleHooks for the MinIO® container(s) to automate configuration before or after startup
|
||
##
|
||
lifecycleHooks: {}
|
||
## @param extraVolumes Optionally specify extra list of additional volumes for MinIO® pods
|
||
##
|
||
extraVolumes: []
|
||
## @param extraVolumeMounts Optionally specify extra list of additional volumeMounts for MinIO® container(s)
|
||
##
|
||
extraVolumeMounts: []
|
||
## @param initContainers Add additional init containers to the MinIO® pods
|
||
## e.g:
|
||
## initContainers:
|
||
## - name: your-image-name
|
||
## image: your-image
|
||
## imagePullPolicy: Always
|
||
## ports:
|
||
## - name: portname
|
||
## containerPort: 1234
|
||
##
|
||
initContainers: []
|
||
## @param sidecars Add additional sidecar containers to the MinIO® pods
|
||
## e.g:
|
||
## sidecars:
|
||
## - name: your-image-name
|
||
## image: your-image
|
||
## imagePullPolicy: Always
|
||
## ports:
|
||
## - name: portname
|
||
## containerPort: 1234
|
||
##
|
||
sidecars: []
|
||
|
||
## @section Traffic exposure parameters
|
||
|
||
## MinIO® Service properties
|
||
##
|
||
service:
|
||
## @param service.type MinIO® service type
|
||
##
|
||
type: ClusterIP
|
||
## @param service.ports.api MinIO® API service port
|
||
## @param service.ports.console MinIO® Console service port
|
||
##
|
||
ports:
|
||
api: 9000
|
||
console: 9001
|
||
## @param service.nodePorts.api Specify the MinIO® API nodePort value for the LoadBalancer and NodePort service types
|
||
## @param service.nodePorts.console Specify the MinIO® Console nodePort value for the LoadBalancer and NodePort service types
|
||
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
|
||
##
|
||
nodePorts:
|
||
api: ""
|
||
console: ""
|
||
## @param service.clusterIP Service Cluster IP
|
||
## e.g.:
|
||
## clusterIP: None
|
||
##
|
||
clusterIP: ""
|
||
## @param service.loadBalancerIP loadBalancerIP if service type is `LoadBalancer` (optional, cloud specific)
|
||
## ref: https://kubernetes.io/docs/user-guide/services/#type-loadbalancer
|
||
##
|
||
loadBalancerIP: ""
|
||
## @param service.loadBalancerSourceRanges Addresses that are allowed when service is LoadBalancer
|
||
## https://kubernetes.io/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/#restrict-access-for-loadbalancer-service
|
||
## e.g:
|
||
## loadBalancerSourceRanges:
|
||
## - 10.10.10.0/24
|
||
##
|
||
loadBalancerSourceRanges: []
|
||
## @param service.externalTrafficPolicy Enable client source IP preservation
|
||
## ref https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip
|
||
##
|
||
externalTrafficPolicy: Cluster
|
||
## @param service.extraPorts Extra ports to expose in the service (normally used with the `sidecar` value)
|
||
##
|
||
extraPorts: []
|
||
## @param service.annotations Annotations for MinIO® service
|
||
## This can be used to set the LoadBalancer service type to internal only.
|
||
## ref: https://kubernetes.io/docs/concepts/services-networking/service/#internal-load-balancer
|
||
##
|
||
annotations: {}
|
||
## Configure the ingress resource that allows you to access the
|
||
## MinIO® Console. Set up the URL
|
||
## ref: https://kubernetes.io/docs/user-guide/ingress/
|
||
##
|
||
ingress:
|
||
## @param ingress.enabled Enable ingress controller resource
|
||
##
|
||
enabled: false
|
||
## @param ingress.apiVersion Force Ingress API version (automatically detected if not set)
|
||
##
|
||
apiVersion: ""
|
||
## @param ingress.ingressClassName IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)
|
||
## This is supported in Kubernetes 1.18+ and required if you have more than one IngressClass marked as the default for your cluster.
|
||
## ref: https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/
|
||
##
|
||
ingressClassName: ""
|
||
## @param ingress.hostname Default host for the ingress resource
|
||
##
|
||
hostname: minio.local
|
||
## @param ingress.path The Path to MinIO®. You may need to set this to '/*' in order to use this with ALB ingress controllers.
|
||
##
|
||
path: /
|
||
## @param ingress.pathType Ingress path type
|
||
##
|
||
pathType: ImplementationSpecific
|
||
## @param ingress.servicePort Service port to be used
|
||
## Default is http. Alternative is https.
|
||
##
|
||
servicePort: minio-console
|
||
## @param ingress.annotations Additional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations.
|
||
## For a full list of possible ingress annotations, please see
|
||
## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md
|
||
## Use this parameter to set the required annotations for cert-manager, see
|
||
## ref: https://cert-manager.io/docs/usage/ingress/#supported-annotations
|
||
##
|
||
## e.g:
|
||
## annotations:
|
||
## kubernetes.io/ingress.class: nginx
|
||
## cert-manager.io/cluster-issuer: cluster-issuer-name
|
||
##
|
||
annotations: {}
|
||
## @param ingress.tls Enable TLS configuration for the hostname defined at `ingress.hostname` parameter
|
||
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.ingress.hostname }}`
|
||
## You can:
|
||
## - Use the `ingress.secrets` parameter to create this TLS secret
|
||
## - Rely on cert-manager to create it by setting the corresponding annotations
|
||
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
|
||
##
|
||
tls: false
|
||
## @param ingress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
|
||
##
|
||
selfSigned: false
|
||
## @param ingress.extraHosts The list of additional hostnames to be covered with this ingress record.
|
||
## Most likely the hostname above will be enough, but in the event more hosts are needed, this is an array
|
||
## e.g:
|
||
## extraHosts:
|
||
## - name: minio.local
|
||
## path: /
|
||
##
|
||
extraHosts: []
|
||
## @param ingress.extraPaths Any additional paths that may need to be added to the ingress under the main host
|
||
## For example: The ALB ingress controller requires a special rule for handling SSL redirection.
|
||
## extraPaths:
|
||
## - path: /*
|
||
## backend:
|
||
## serviceName: ssl-redirect
|
||
## servicePort: use-annotation
|
||
##
|
||
extraPaths: []
|
||
## @param ingress.extraTls The tls configuration for additional hostnames to be covered with this ingress record.
|
||
## see: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
|
||
## e.g:
|
||
## extraTls:
|
||
## - hosts:
|
||
## - minio.local
|
||
## secretName: minio.local-tls
|
||
##
|
||
extraTls: []
|
||
## @param ingress.secrets If you're providing your own certificates, please use this to add the certificates as secrets
|
||
## key and certificate are expected in PEM format
|
||
## name should line up with a secretName set further up
|
||
##
|
||
## If it is not set and you're using cert-manager, this is unneeded, as it will create a secret for you with valid certificates
|
||
## If it is not set and you're NOT using cert-manager either, self-signed certificates will be created valid for 365 days
|
||
## It is also possible to create and manage the certificates outside of this helm chart
|
||
## Please see README.md for more information
|
||
##
|
||
## Example
|
||
## secrets:
|
||
## - name: minio.local-tls
|
||
## key: ""
|
||
## certificate: ""
|
||
##
|
||
secrets: []
|
||
## @param ingress.extraRules Additional rules to be covered with this ingress record
|
||
## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-rules
|
||
## e.g:
|
||
## extraRules:
|
||
## - host: example.local
|
||
## http:
|
||
## path: /
|
||
## backend:
|
||
## service:
|
||
## name: example-svc
|
||
## port:
|
||
## name: http
|
||
##
|
||
extraRules: []
|
||
|
||
## Configure the ingress resource that allows you to access the
|
||
## MinIO® API. Set up the URL
|
||
## ref: https://kubernetes.io/docs/user-guide/ingress/
|
||
##
|
||
apiIngress:
|
||
## @param apiIngress.enabled Enable ingress controller resource
|
||
##
|
||
enabled: false
|
||
## @param apiIngress.apiVersion Force Ingress API version (automatically detected if not set)
|
||
##
|
||
apiVersion: ""
|
||
## @param apiIngress.ingressClassName IngressClass that will be be used to implement the Ingress (Kubernetes 1.18+)
|
||
## This is supported in Kubernetes 1.18+ and required if you have more than one IngressClass marked as the default for your cluster.
|
||
## ref: https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/
|
||
##
|
||
ingressClassName: ""
|
||
## @param apiIngress.hostname Default host for the ingress resource
|
||
##
|
||
hostname: minio.local
|
||
## @param apiIngress.path The Path to MinIO®. You may need to set this to '/*' in order to use this with ALB ingress controllers.
|
||
##
|
||
path: /
|
||
## @param apiIngress.pathType Ingress path type
|
||
##
|
||
pathType: ImplementationSpecific
|
||
## @param apiIngress.servicePort Service port to be used
|
||
## Default is http. Alternative is https.
|
||
##
|
||
servicePort: minio-api
|
||
## @param apiIngress.annotations Additional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations.
|
||
## For a full list of possible ingress annotations, please see
|
||
## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md
|
||
## Use this parameter to set the required annotations for cert-manager, see
|
||
## ref: https://cert-manager.io/docs/usage/ingress/#supported-annotations
|
||
##
|
||
## e.g:
|
||
## annotations:
|
||
## kubernetes.io/ingress.class: nginx
|
||
## cert-manager.io/cluster-issuer: cluster-issuer-name
|
||
##
|
||
annotations: {}
|
||
## @param apiIngress.tls Enable TLS configuration for the hostname defined at `apiIngress.hostname` parameter
|
||
## TLS certificates will be retrieved from a TLS secret with name: `{{- printf "%s-tls" .Values.apiIngress.hostname }}`
|
||
## You can:
|
||
## - Use the `ingress.secrets` parameter to create this TLS secret
|
||
## - Rely on cert-manager to create it by setting the corresponding annotations
|
||
## - Rely on Helm to create self-signed certificates by setting `ingress.selfSigned=true`
|
||
##
|
||
tls: false
|
||
## @param apiIngress.selfSigned Create a TLS secret for this ingress record using self-signed certificates generated by Helm
|
||
##
|
||
selfSigned: false
|
||
## @param apiIngress.extraHosts The list of additional hostnames to be covered with this ingress record.
|
||
## Most likely the hostname above will be enough, but in the event more hosts are needed, this is an array
|
||
## e.g:
|
||
## extraHosts:
|
||
## - name: minio.local
|
||
## path: /
|
||
##
|
||
extraHosts: []
|
||
## @param apiIngress.extraPaths Any additional paths that may need to be added to the ingress under the main host
|
||
## For example: The ALB ingress controller requires a special rule for handling SSL redirection.
|
||
## extraPaths:
|
||
## - path: /*
|
||
## backend:
|
||
## serviceName: ssl-redirect
|
||
## servicePort: use-annotation
|
||
##
|
||
extraPaths: []
|
||
## @param apiIngress.extraTls The tls configuration for additional hostnames to be covered with this ingress record.
|
||
## see: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls
|
||
## e.g:
|
||
## extraTls:
|
||
## - hosts:
|
||
## - minio.local
|
||
## secretName: minio.local-tls
|
||
##
|
||
extraTls: []
|
||
## @param apiIngress.secrets If you're providing your own certificates, please use this to add the certificates as secrets
|
||
## key and certificate are expected in PEM format
|
||
## name should line up with a secretName set further up
|
||
##
|
||
## If it is not set and you're using cert-manager, this is unneeded, as it will create a secret for you with valid certificates
|
||
## If it is not set and you're NOT using cert-manager either, self-signed certificates will be created valid for 365 days
|
||
## It is also possible to create and manage the certificates outside of this helm chart
|
||
## Please see README.md for more information
|
||
##
|
||
## Example
|
||
## secrets:
|
||
## - name: minio.local-tls
|
||
## key: ""
|
||
## certificate: ""
|
||
##
|
||
secrets: []
|
||
|
||
## NetworkPolicy parameters
|
||
##
|
||
networkPolicy:
|
||
## @param networkPolicy.enabled Enable the default NetworkPolicy policy
|
||
##
|
||
enabled: false
|
||
## @param networkPolicy.allowExternal Don't require client label for connections
|
||
## When set to false, only pods with the correct client label will have network access to the port MinIO® is
|
||
## listening on. When true, MinIO® will accept connections from any source (with the correct destination port).
|
||
##
|
||
allowExternal: true
|
||
## @param networkPolicy.extraFromClauses Allows to add extra 'from' clauses to the NetworkPolicy
|
||
extraFromClauses: {}
|
||
## Example
|
||
## extraFromClauses:
|
||
## - podSelector:
|
||
## matchLabels:
|
||
## a: b
|
||
|
||
## @section Persistence parameters
|
||
|
||
## Enable persistence using Persistent Volume Claims
|
||
## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/
|
||
##
|
||
persistence:
|
||
## @param persistence.enabled Enable MinIO® data persistence using PVC. If false, use emptyDir
|
||
##
|
||
enabled: true
|
||
## @param persistence.storageClass PVC Storage Class for MinIO® data volume
|
||
## If defined, storageClassName: <storageClass>
|
||
## If set to "-", storageClassName: "", which disables dynamic provisioning
|
||
## If undefined (the default) or set to null, no storageClassName spec is
|
||
## set, choosing the default provisioner. (gp2 on AWS, standard on
|
||
## GKE, AWS & OpenStack)
|
||
##
|
||
storageClass: ""
|
||
## @param persistence.mountPath Data volume mount path
|
||
##
|
||
mountPath: /data
|
||
## @param persistence.accessModes PVC Access Modes for MinIO® data volume
|
||
##
|
||
accessModes:
|
||
- ReadWriteOnce
|
||
## @param persistence.size PVC Storage Request for MinIO® data volume
|
||
##
|
||
size: 8Gi
|
||
## @param persistence.annotations Annotations for the PVC
|
||
##
|
||
annotations: {}
|
||
## @param persistence.existingClaim Name of an existing PVC to use (only in `standalone` mode)
|
||
##
|
||
existingClaim: ""
|
||
|
||
## @section Volume Permissions parameters
|
||
|
||
## Init containers parameters:
|
||
## volumePermissions: Change the owner and group of the persistent volume mountpoint to runAsUser:fsGroup values from the securityContext section.
|
||
##
|
||
volumePermissions:
|
||
## @param volumePermissions.enabled Enable init container that changes the owner and group of the persistent volume(s) mountpoint to `runAsUser:fsGroup`
|
||
##
|
||
enabled: false
|
||
## @param volumePermissions.image.registry Init container volume-permissions image registry
|
||
## @param volumePermissions.image.repository Init container volume-permissions image repository
|
||
## @param volumePermissions.image.tag Init container volume-permissions image tag (immutable tags are recommended)
|
||
## @param volumePermissions.image.pullPolicy Init container volume-permissions image pull policy
|
||
## @param volumePermissions.image.pullSecrets Specify docker-registry secret names as an array
|
||
##
|
||
image:
|
||
registry: docker.io
|
||
repository: bitnami/bitnami-shell
|
||
tag: 10-debian-10-r433
|
||
pullPolicy: IfNotPresent
|
||
## Optionally specify an array of imagePullSecrets.
|
||
## Secrets must be manually created in the namespace.
|
||
## ref: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/
|
||
## e.g:
|
||
## pullSecrets:
|
||
## - myRegistryKeySecretName
|
||
##
|
||
pullSecrets: []
|
||
## Init container' resource requests and limits
|
||
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
|
||
## We usually recommend not to specify default resources and to leave this as a conscious
|
||
## choice for the user. This also increases chances charts run on environments with little
|
||
## resources, such as Minikube. If you do want to specify resources, uncomment the following
|
||
## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
|
||
## @param volumePermissions.resources.limits Init container volume-permissions resource limits
|
||
## @param volumePermissions.resources.requests Init container volume-permissions resource requests
|
||
##
|
||
resources:
|
||
## Example:
|
||
## limits:
|
||
## cpu: 500m
|
||
## memory: 1Gi
|
||
limits: {}
|
||
requests: {}
|
||
## Init container' Security Context
|
||
## Note: the chown of the data folder is done to containerSecurityContext.runAsUser
|
||
## and not the below volumePermissions.containerSecurityContext.runAsUser
|
||
## @param volumePermissions.containerSecurityContext.runAsUser User ID for the init container
|
||
##
|
||
containerSecurityContext:
|
||
runAsUser: 0
|
||
|
||
## @section RBAC parameters
|
||
|
||
## Specifies whether a ServiceAccount should be created
|
||
##
|
||
serviceAccount:
|
||
## @param serviceAccount.create Enable the creation of a ServiceAccount for MinIO® pods
|
||
##
|
||
create: true
|
||
## @param serviceAccount.name Name of the created ServiceAccount
|
||
## If not set and create is true, a name is generated using the common.names.fullname template
|
||
##
|
||
name: ""
|
||
## @param serviceAccount.automountServiceAccountToken Enable/disable auto mounting of the service account token
|
||
##
|
||
automountServiceAccountToken: true
|
||
## @param serviceAccount.annotations Custom annotations for MinIO® ServiceAccount
|
||
##
|
||
annotations: {}
|
||
|
||
## @section Other parameters
|
||
|
||
## MinIO® Pod Disruption Budget configuration in distributed mode.
|
||
## If MinIO® Gateway is enabled, creates a Pod Disruption Budget for the Gateway instead (mutually exclusive with distributed mode).
|
||
## ref: https://kubernetes.io/docs/tasks/run-application/configure-pdb/
|
||
##
|
||
pdb:
|
||
## @param pdb.create Enable/disable a Pod Disruption Budget creation
|
||
##
|
||
create: false
|
||
## @param pdb.minAvailable Minimum number/percentage of pods that must still be available after the eviction
|
||
##
|
||
minAvailable: 1
|
||
## @param pdb.maxUnavailable Maximum number/percentage of pods that may be made unavailable after the eviction
|
||
##
|
||
maxUnavailable: ""
|
||
|
||
## @section Metrics parameters
|
||
|
||
metrics:
|
||
## @param metrics.prometheusAuthType Authentication mode for Prometheus (`jwt` or `public`)
|
||
## To allow public access without authentication for prometheus metrics set environment as follows.
|
||
##
|
||
prometheusAuthType: public
|
||
## Prometheus Operator ServiceMonitor configuration
|
||
##
|
||
serviceMonitor:
|
||
## @param metrics.serviceMonitor.enabled If the operator is installed in your cluster, set to true to create a Service Monitor Entry
|
||
##
|
||
enabled: false
|
||
## @param metrics.serviceMonitor.namespace Namespace which Prometheus is running in
|
||
##
|
||
namespace: ""
|
||
## @param metrics.serviceMonitor.labels Extra labels for the ServiceMonitor
|
||
##
|
||
labels: {}
|
||
## @param metrics.serviceMonitor.jobLabel The name of the label on the target service to use as the job name in Prometheus
|
||
##
|
||
jobLabel: ""
|
||
## @param metrics.serviceMonitor.path HTTP path to scrape for metrics
|
||
##
|
||
path: /minio/v2/metrics/cluster
|
||
## @param metrics.serviceMonitor.interval Interval at which metrics should be scraped
|
||
##
|
||
interval: 30s
|
||
## @param metrics.serviceMonitor.scrapeTimeout Specify the timeout after which the scrape is ended
|
||
## e.g:
|
||
## scrapeTimeout: 30s
|
||
scrapeTimeout: ""
|
||
## @param metrics.serviceMonitor.metricRelabelings MetricRelabelConfigs to apply to samples before ingestion
|
||
##
|
||
metricRelabelings: []
|
||
## @param metrics.serviceMonitor.relabelings Metrics relabelings to add to the scrape endpoint, applied before scraping
|
||
##
|
||
relabelings: []
|
||
## @param metrics.serviceMonitor.honorLabels Specify honorLabels parameter to add the scrape endpoint
|
||
##
|
||
honorLabels: false
|
||
## @param metrics.serviceMonitor.selector Prometheus instance selector labels
|
||
## ref: https://github.com/bitnami/charts/tree/master/bitnami/prometheus-operator#prometheus-configuration
|
||
##
|
||
selector: {}
|
||
|
||
## Prometheus Operator PrometheusRule configuration
|
||
##
|
||
prometheusRule:
|
||
## @param metrics.prometheusRule.enabled Create a Prometheus Operator PrometheusRule (also requires `metrics.enabled` to be `true` and `metrics.prometheusRule.rules`)
|
||
##
|
||
enabled: false
|
||
## @param metrics.prometheusRule.namespace Namespace for the PrometheusRule Resource (defaults to the Release Namespace)
|
||
##
|
||
namespace: ""
|
||
## @param metrics.prometheusRule.additionalLabels Additional labels that can be used so PrometheusRule will be discovered by Prometheus
|
||
##
|
||
additionalLabels: {}
|
||
## @param metrics.prometheusRule.rules Prometheus Rule definitions
|
||
# - alert: minio cluster nodes offline
|
||
# annotations:
|
||
# summary: "minio cluster nodes offline"
|
||
# description: "minio cluster nodes offline，pod {{`{{`}} $labels.pod {{`}}`}} service {{`{{`}} $labels.job {{`}}`}} offline"
|
||
# for: 10m
|
||
# expr: minio_cluster_nodes_offline_total > 0
|
||
# labels:
|
||
# severity: critical
|
||
# group: PaaS
|
||
##
|
||
rules: []
|
||
|
||
## @section Gateway parameters
|
||
|
||
gateway:
|
||
## @param gateway.enabled Use MinIO® as Gateway for other storage systems
|
||
##
|
||
enabled: false
|
||
## @param gateway.type Gateway type. Supported types are: `azure`, `gcs`, `nas`, `s3`
|
||
## ref: https://docs.minio.io/docs/minio-gateway-for-azure
|
||
## ref: https://docs.minio.io/docs/minio-gateway-for-gcs
|
||
## ref: https://docs.minio.io/docs/minio-gateway-for-nas
|
||
## ref: https://docs.minio.io/docs/minio-gateway-for-s3
|
||
##
|
||
type: s3
|
||
## @param gateway.replicaCount Number of MinIO® Gateway replicas
|
||
##
|
||
replicaCount: 4
|
||
## @param gateway.updateStrategy.type Update strategy type for MinIO® Gateway replicas
|
||
updateStrategy:
|
||
type: Recreate
|
||
## Autoscaling configuration for MinIO® Gateway. overrides gateway.replicaCount if enabled
|
||
## @param gateway.autoscaling.enabled Enable autoscaling for MinIO® Gateway deployment
|
||
## @param gateway.autoscaling.minReplicas Minimum number of replicas to scale back
|
||
## @param gateway.autoscaling.maxReplicas Maximum number of replicas to scale out
|
||
## @param gateway.autoscaling.targetCPU Target CPU utilization percentage
|
||
## @param gateway.autoscaling.targetMemory Target Memory utilization percentage
|
||
autoscaling:
|
||
enabled: false
|
||
minReplicas: "4"
|
||
maxReplicas: "4"
|
||
targetCPU: ""
|
||
targetMemory: ""
|
||
## @param gateway.priorityClassName Pod priority class name for MinIO® Gateway
|
||
##
|
||
priorityClassName: ""
|
||
## Gateway authentication configuration
|
||
##
|
||
auth:
|
||
## Authentication configuration for Azure. Ignored unless type=azure
|
||
## @param gateway.auth.azure.accessKey Access key to access MinIO® using Azure Gateway
|
||
## @param gateway.auth.azure.secretKey Secret key to access MinIO® using Azure Gateway
|
||
## @param gateway.auth.azure.serviceEndpoint Azure Blob Storage custom endpoint
|
||
## @param gateway.auth.azure.storageAccountName Azure Storage Account Name to use to access Azure Blob Storage
|
||
## @param gateway.auth.azure.storageAccountKey Azure Storage Account Key to use to access Azure Blob Storage
|
||
## @param gateway.auth.azure.storageAccountNameExistingSecret Existing Secret name to extract Azure Storage Account Name from to access Azure Blob Storage
|
||
## @param gateway.auth.azure.storageAccountNameExistingSecretKey Existing Secret key to extract Azure Storage Account Name from to use to access Azure Blob Storage
|
||
## @param gateway.auth.azure.storageAccountKeyExistingSecret Existing Secret name to extract Azure Storage Account Key from to access Azure Blob Storage
|
||
## @param gateway.auth.azure.storageAccountKeyExistingSecretKey Existing Secret key to extract Azure Storage Account Key from to use to access Azure Blob Storage
|
||
##
|
||
azure:
|
||
accessKey: ""
|
||
secretKey: ""
|
||
serviceEndpoint: ""
|
||
storageAccountName: ""
|
||
storageAccountKey: ""
|
||
storageAccountNameExistingSecret: ""
|
||
storageAccountNameExistingSecretKey: ""
|
||
storageAccountKeyExistingSecret: ""
|
||
storageAccountKeyExistingSecretKey: ""
|
||
## Authentication configuration for GCS. Ignored unless type=gcs
|
||
## @param gateway.auth.gcs.accessKey Access key to access MinIO® using GCS Gateway
|
||
## @param gateway.auth.gcs.secretKey Secret key to access MinIO® using GCS Gateway
|
||
## @param gateway.auth.gcs.keyJSON Service Account key to access GCS
|
||
## @param gateway.auth.gcs.projectID GCP Project ID to use
|
||
##
|
||
gcs:
|
||
accessKey: ""
|
||
secretKey: ""
|
||
keyJSON: ""
|
||
projectID: ""
|
||
## Authentication configuration for NAS. Ignored unless type=nas
|
||
## @param gateway.auth.nas.accessKey Access key to access MinIO® using NAS Gateway
|
||
## @param gateway.auth.nas.secretKey Secret key to access MinIO® using NAS Gateway
|
||
##
|
||
nas:
|
||
accessKey: ""
|
||
secretKey: ""
|
||
## Authentication configuration for S3. Ignored unless type=s3
|
||
## @param gateway.auth.s3.accessKey Access key to use to access AWS S3
|
||
## @param gateway.auth.s3.secretKey Secret key to use to access AWS S3
|
||
## @param gateway.auth.s3.serviceEndpoint AWS S3 endpoint
|
||
##
|
||
s3:
|
||
accessKey: ""
|
||
secretKey: ""
|
||
serviceEndpoint: https://s3.amazonaws.com
|