Repast content values-tenant.yaml 11

This commit is contained in:
Ruben Hensen
2024-09-10 00:15:26 +02:00
parent b51e15d8e5
commit 4c0aaa55f2
+180 -180
View File
@@ -181,167 +181,167 @@ tenant:
#
# The name of a custom `Container Runtime <https://kubernetes.io/docs/concepts/containers/runtime-class/>`__ to use for the Operator Console pods.
# runtimeClassName: ""
###
# The mount path where Persistent Volumes are mounted inside Tenant container(s).
mountPath: /export
###
# The Sub path inside Mount path where MinIO stores data.
#
# .. warning::
#
# Treat the ``mountPath`` and ``subPath`` values as immutable once you deploy the Tenant.
# If you change these values post-deployment, then you may have different paths for new and pre-existing data.
# This can vastly increase operational complexity and may result in unpredictable data states.
subPath: /data
###
# Configures a Prometheus-compatible scraping endpoint at the specified port.
metrics:
enabled: false
port: 9000
protocol: http
###
# Configures external certificate settings for the Tenant.
certificate:
###
# Specify an array of Kubernetes TLS secrets, where each entry corresponds to a secret the TLS private key and public certificate pair.
#
# This is used by MinIO to verify TLS connections from clients using those CAs
# If you omit this and have clients using TLS certificates minted by an external CA, those connections may fail with warnings around certificate verification.
# See `Operator CRD: TenantSpec <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#tenantspec>`__.
externalCaCertSecret: [ ]
###
# Specify an array of Kubernetes secrets, where each entry corresponds to a secret contains the TLS private key and public certificate pair.
#
# Omit this to use only the MinIO Operator autogenerated certificates.
#
# If you omit this field *and* set ``requestAutoCert`` to false, the Tenant starts without TLS.
#
# See `Operator CRD: TenantSpec <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#tenantspec>`__.
#
# .. important::
#
# The MinIO Operator may output TLS connectivity errors if it cannot trust the Certificate Authority (CA) which minted the custom certificates.
#
# You can pass the CA to the Operator to allow it to trust that cert.
# See `Self-Signed, Internal, and Private Certificates <https://min.io/docs/minio/kubernetes/upstream/operations/network-encryption.html#self-signed-internal-and-private-certificates>`__ for more information.
# This step may also be necessary for globally trusted CAs where you must provide intermediate certificates to the Operator to help build the full chain of trust.
externalCertSecret: [ ]
###
# Enable automatic Kubernetes based `certificate generation and signing <https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster>`__
requestAutoCert: true
###
# The minimum number of days to expiry before an alert for an expiring certificate is fired.
# In the below example, if a given certificate will expire in 7 days then expiration events will only be triggered 1 day before expiry
# certExpiryAlertThreshold: 1
###
# This field is used only when ``requestAutoCert: true``.
# Use this field to set CommonName for the auto-generated certificate.
# MinIO defaults to using the internal Kubernetes DNS name for the pod
# The default DNS name format is typically ``*.minio.default.svc.cluster.local``.
#
# See `Operator CRD: CertificateConfig <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#certificateconfig>`__
certConfig: { }
###
# MinIO features to enable or disable in the MinIO Tenant
# See `Operator CRD: Features <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#features>`__.
features:
bucketDNS: false
domains: { }
enableSFTP: false
###
# Array of objects describing one or more buckets to create during tenant provisioning.
# Example:
#
# .. code-block:: yaml
#
# - name: my-minio-bucket
# objectLock: false # optional
# region: us-east-1 # optional
buckets: [ ]
###
# Array of Kubernetes secrets from which the Operator generates MinIO users during tenant provisioning.
#
# Each secret should specify the ``CONSOLE_ACCESS_KEY`` and ``CONSOLE_SECRET_KEY`` as the access key and secret key for that user.
users: [ ]
###
# The `PodManagement <https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#pod-management-policy>`__ policy for MinIO Tenant Pods.
# Can be "OrderedReady" or "Parallel"
podManagementPolicy: Parallel
# The `Liveness Probe <https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes>`__ for monitoring Tenant pod liveness.
# Tenant pods will be restarted if the probe fails.
liveness: { }
###
# `Readiness Probe <https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/>`__ for monitoring Tenant container readiness.
# Tenant pods will be removed from service endpoints if the probe fails.
readiness: { }
###
# `Startup Probe <https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/>`__ for monitoring container startup.
# Tenant pods will be restarted if the probe fails.
# Refer
startup: { }
###
# The `Lifecycle hooks <https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/>`__ for container.
lifecycle: { }
###
# Directs the Operator to deploy the MinIO S3 API and Console services as LoadBalancer objects.
#
# If the Kubernetes cluster has a configured LoadBalancer, it can attempt to route traffic to those services automatically.
#
# - Specify ``minio: true`` to expose the MinIO S3 API.
# - Specify ``console: true`` to expose the Console.
#
# Both fields default to ``false``.
exposeServices: { }
###
# The `Kubernetes Service Account <https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/>`__ associated with the Tenant.
serviceAccountName: ""
###
# Directs the Operator to add the Tenant's metric scrape configuration to an existing Kubernetes Prometheus deployment managed by the Prometheus Operator.
prometheusOperator: false
###
# Configure pod logging configuration for the MinIO Tenant.
#
# - Specify ``json`` for JSON-formatted logs.
# - Specify ``anonymous`` for anonymized logs.
# - Specify ``quiet`` to supress logging.
#
# An example of JSON-formatted logs is as follows:
#
# .. code-block:: shell
#
# $ k logs myminio-pool-0-0 -n default
# {"level":"INFO","errKind":"","time":"2022-04-07T21:49:33.740058549Z","message":"All MinIO sub-systems initialized successfully"}
logging: { }
###
# serviceMetadata allows passing additional labels and annotations to MinIO and Console specific
# services created by the operator.
serviceMetadata: { }
###
# Add environment variables to be set in MinIO container (https://github.com/minio/minio/tree/master/docs/config)
env: [ ]
###
# PriorityClassName indicates the Pod priority and hence importance of a Pod relative to other Pods.
# This is applied to MinIO pods only.
# Refer Kubernetes documentation for details https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass/
priorityClassName: ""
###
# An array of `Volumes <https://kubernetes.io/docs/concepts/storage/volumes/>`__ which the Operator can mount to Tenant pods.
#
# The volumes must exist *and* be accessible to the Tenant pods.
additionalVolumes: [ ]
###
# An array of volume mount points associated to each Tenant container.
#
# Specify each item in the array as follows:
#
# .. code-block:: yaml
#
# volumeMounts:
# - name: volumename
# mountPath: /path/to/mount
#
# The ``name`` field must correspond to an entry in the ``additionalVolumes`` array.
additionalVolumeMounts: [ ]
# ###
# # The mount path where Persistent Volumes are mounted inside Tenant container(s).
# mountPath: /export
# ###
# # The Sub path inside Mount path where MinIO stores data.
# #
# # .. warning::
# #
# # Treat the ``mountPath`` and ``subPath`` values as immutable once you deploy the Tenant.
# # If you change these values post-deployment, then you may have different paths for new and pre-existing data.
# # This can vastly increase operational complexity and may result in unpredictable data states.
# subPath: /data
# ###
# # Configures a Prometheus-compatible scraping endpoint at the specified port.
# metrics:
# enabled: false
# port: 9000
# protocol: http
# ###
# # Configures external certificate settings for the Tenant.
# certificate:
# ###
# # Specify an array of Kubernetes TLS secrets, where each entry corresponds to a secret the TLS private key and public certificate pair.
# #
# # This is used by MinIO to verify TLS connections from clients using those CAs
# # If you omit this and have clients using TLS certificates minted by an external CA, those connections may fail with warnings around certificate verification.
# # See `Operator CRD: TenantSpec <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#tenantspec>`__.
# externalCaCertSecret: [ ]
# ###
# # Specify an array of Kubernetes secrets, where each entry corresponds to a secret contains the TLS private key and public certificate pair.
# #
# # Omit this to use only the MinIO Operator autogenerated certificates.
# #
# # If you omit this field *and* set ``requestAutoCert`` to false, the Tenant starts without TLS.
# #
# # See `Operator CRD: TenantSpec <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#tenantspec>`__.
# #
# # .. important::
# #
# # The MinIO Operator may output TLS connectivity errors if it cannot trust the Certificate Authority (CA) which minted the custom certificates.
# #
# # You can pass the CA to the Operator to allow it to trust that cert.
# # See `Self-Signed, Internal, and Private Certificates <https://min.io/docs/minio/kubernetes/upstream/operations/network-encryption.html#self-signed-internal-and-private-certificates>`__ for more information.
# # This step may also be necessary for globally trusted CAs where you must provide intermediate certificates to the Operator to help build the full chain of trust.
# externalCertSecret: [ ]
# ###
# # Enable automatic Kubernetes based `certificate generation and signing <https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster>`__
# requestAutoCert: true
# ###
# # The minimum number of days to expiry before an alert for an expiring certificate is fired.
# # In the below example, if a given certificate will expire in 7 days then expiration events will only be triggered 1 day before expiry
# # certExpiryAlertThreshold: 1
# ###
# # This field is used only when ``requestAutoCert: true``.
# # Use this field to set CommonName for the auto-generated certificate.
# # MinIO defaults to using the internal Kubernetes DNS name for the pod
# # The default DNS name format is typically ``*.minio.default.svc.cluster.local``.
# #
# # See `Operator CRD: CertificateConfig <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#certificateconfig>`__
# certConfig: { }
# ###
# # MinIO features to enable or disable in the MinIO Tenant
# # See `Operator CRD: Features <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#features>`__.
# features:
# bucketDNS: false
# domains: { }
# enableSFTP: false
# ###
# # Array of objects describing one or more buckets to create during tenant provisioning.
# # Example:
# #
# # .. code-block:: yaml
# #
# # - name: my-minio-bucket
# # objectLock: false # optional
# # region: us-east-1 # optional
# buckets: [ ]
# ###
# # Array of Kubernetes secrets from which the Operator generates MinIO users during tenant provisioning.
# #
# # Each secret should specify the ``CONSOLE_ACCESS_KEY`` and ``CONSOLE_SECRET_KEY`` as the access key and secret key for that user.
# users: [ ]
# ###
# # The `PodManagement <https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#pod-management-policy>`__ policy for MinIO Tenant Pods.
# # Can be "OrderedReady" or "Parallel"
# podManagementPolicy: Parallel
# # The `Liveness Probe <https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes>`__ for monitoring Tenant pod liveness.
# # Tenant pods will be restarted if the probe fails.
# liveness: { }
# ###
# # `Readiness Probe <https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/>`__ for monitoring Tenant container readiness.
# # Tenant pods will be removed from service endpoints if the probe fails.
# readiness: { }
# ###
# # `Startup Probe <https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/>`__ for monitoring container startup.
# # Tenant pods will be restarted if the probe fails.
# # Refer
# startup: { }
# ###
# # The `Lifecycle hooks <https://kubernetes.io/docs/concepts/containers/container-lifecycle-hooks/>`__ for container.
# lifecycle: { }
# ###
# # Directs the Operator to deploy the MinIO S3 API and Console services as LoadBalancer objects.
# #
# # If the Kubernetes cluster has a configured LoadBalancer, it can attempt to route traffic to those services automatically.
# #
# # - Specify ``minio: true`` to expose the MinIO S3 API.
# # - Specify ``console: true`` to expose the Console.
# #
# # Both fields default to ``false``.
# exposeServices: { }
# ###
# # The `Kubernetes Service Account <https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/>`__ associated with the Tenant.
# serviceAccountName: ""
# ###
# # Directs the Operator to add the Tenant's metric scrape configuration to an existing Kubernetes Prometheus deployment managed by the Prometheus Operator.
# prometheusOperator: false
# ###
# # Configure pod logging configuration for the MinIO Tenant.
# #
# # - Specify ``json`` for JSON-formatted logs.
# # - Specify ``anonymous`` for anonymized logs.
# # - Specify ``quiet`` to supress logging.
# #
# # An example of JSON-formatted logs is as follows:
# #
# # .. code-block:: shell
# #
# # $ k logs myminio-pool-0-0 -n default
# # {"level":"INFO","errKind":"","time":"2022-04-07T21:49:33.740058549Z","message":"All MinIO sub-systems initialized successfully"}
# logging: { }
# ###
# # serviceMetadata allows passing additional labels and annotations to MinIO and Console specific
# # services created by the operator.
# serviceMetadata: { }
# ###
# # Add environment variables to be set in MinIO container (https://github.com/minio/minio/tree/master/docs/config)
# env: [ ]
# ###
# # PriorityClassName indicates the Pod priority and hence importance of a Pod relative to other Pods.
# # This is applied to MinIO pods only.
# # Refer Kubernetes documentation for details https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass/
# priorityClassName: ""
# ###
# # An array of `Volumes <https://kubernetes.io/docs/concepts/storage/volumes/>`__ which the Operator can mount to Tenant pods.
# #
# # The volumes must exist *and* be accessible to the Tenant pods.
# additionalVolumes: [ ]
# ###
# # An array of volume mount points associated to each Tenant container.
# #
# # Specify each item in the array as follows:
# #
# # .. code-block:: yaml
# #
# # volumeMounts:
# # - name: volumename
# # mountPath: /path/to/mount
# #
# # The ``name`` field must correspond to an entry in the ``additionalVolumes`` array.
# additionalVolumeMounts: [ ]
# Define configuration for KES (stateless and distributed key-management system)
# Refer https://github.com/minio/kes
#kes:
@@ -444,25 +444,25 @@ tenant:
# Configures `Ingress <https://kubernetes.io/docs/concepts/services-networking/ingress/>`__ for the Tenant S3 API and Console.
#
# Set the keys to conform to the Ingress controller and configuration of your choice.
# ingress:
# api:
# enabled: false
# ingressClassName: ""
# labels: { }
# annotations: { }
# tls: [ ]
# host: minio.local
# path: /
# pathType: Prefix
# console:
# enabled: false
# ingressClassName: ""
# labels: { }
# annotations: { }
# tls: [ ]
# host: minio-console.local
# path: /
# pathType: Prefix
ingress:
api:
enabled: false
ingressClassName: ""
labels: { }
annotations: { }
tls: [ ]
host: minio.local
path: /
pathType: Prefix
console:
enabled: false
ingressClassName: ""
labels: { }
annotations: { }
tls: [ ]
host: minio-console.local
path: /
pathType: Prefix
# Use an extraResources template section to include additional Kubernetes resources
# with the Helm deployment.
#extraResources: