Remove _ and ### from values

minio/values-tenant.yaml

@@ -1,11 +1,11 @@
 # Root key for MinIO Tenant Chart
 tenant:
-  ###
+  
   # The Tenant name
   #
   # Change this to match your preferred MinIO Tenant name.
   name: myminio
-  ###
+  
   # Specify the Operator container image to use for the deployment.
   # ``image.tag`` 
   # For example, the following sets the image to the ``quay.io/minio/operator`` repo and the v6.0.3 tag.
@@ -32,22 +32,22 @@ tenant:
     repository: quay.io/minio/minio
     tag: RELEASE.2024-08-17T01-24-54Z
     pullPolicy: IfNotPresent
-  ###
+  
   #
   # An array of Kubernetes secrets to use for pulling images from a private ``image.repository``.
   # Only one array element is supported at this time.
   imagePullSecret: { }
-  ###
+  
-  # The Kubernetes `Scheduler <https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/>`__ to use for dispatching Tenant pods.
+  # The Kubernetes `Scheduler <https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/>` to use for dispatching Tenant pods.
   #
   # Specify an empty dictionary ``{}`` to dispatch pods with the default scheduler.
   scheduler: { }
-  ###
+  
   # The Kubernetes secret name that contains MinIO environment variable configurations.
   # The secret is expected to have a key named config.env containing environment variables exports.
   configuration:
     name: myminio-env-configuration
-  ###
+  
   # Root key for dynamically creating a secret for use with configuring root MinIO User
   # Specify the ``name`` and then a list of environment variables.
   #
@@ -70,7 +70,7 @@ tenant:
     secretKey: minio123
     #existingSecret: true
 
-  ###
+  
   # If this variable is set to true, then enable the usage of an existing Kubernetes secret to set environment variables for the Tenant.
   # The existing Kubernetes secret name must be placed under .tenant.configuration.name e.g. existing-minio-env-configuration
   # The secret must contain a key ``config.env``.
@@ -81,73 +81,73 @@ tenant:
   #
   #    stringData:
   #       config.env: |-
-  #         export MINIO_ROOT_USER=ROOTUSERNAME
+  #         export MINIOROOTUSER=ROOTUSERNAME
-  #         export MINIO_ROOT_PASSWORD=ROOTUSERPASSWORD
+  #         export MINIOROOTPASSWORD=ROOTUSERPASSWORD
   #
   #   existingSecret: false
-  ###
+  
   # Top level key for configuring MinIO Pool(s) in this Tenant.
   #
-  # See `Operator CRD: Pools <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#pool>`__ for more information on all subfields.
+  # See `Operator CRD: Pools <https://min.io/docs/minio/kubernetes/upstream/reference/operator-crd.html#pool>` for more information on all subfields.
   pools:
-    ###
+    
     # The number of MinIO Tenant Pods / Servers in this pool.
     # For standalone mode, supply 1. For distributed mode, supply 4 or more.
     # Note that the operator does not support upgrading from standalone to distributed mode.
     - servers: 1
-      ###
+      
       # Custom name for the pool
       name: pool-0
-      ###
+      
       # The number of volumes attached per MinIO Tenant Pod / Server.
       volumesPerServer: 1
-      ###
+      
       # The capacity per volume requested per MinIO Tenant Pod.
       size: 10Gi
-      ###
+      
-      # The `storageClass <https://kubernetes.io/docs/concepts/storage/storage-classes/>`__ to associate with volumes generated for this pool.
+      # The `storageClass <https://kubernetes.io/docs/concepts/storage/storage-classes/>` to associate with volumes generated for this pool.
       #
       # If using Amazon Elastic Block Store (EBS) CSI driver
       # Please make sure to set xfs for "csi.storage.k8s.io/fstype" parameter under StorageClass.parameters.
       # Docs: https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/docs/parameters.md
       # storageClassName: standard
-      ###
+      
-      # Specify `storageAnnotations <https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/>`__ to associate to PVCs.
+      # Specify `storageAnnotations <https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/>` to associate to PVCs.
       storageAnnotations: { }
-      ###
+      
-      # Specify `annotations <https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/>`__ to associate to Tenant pods.
+      # Specify `annotations <https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/>` to associate to Tenant pods.
       annotations: { }
-      ###
+      
-      # Specify `labels <https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/>`__ to associate to Tenant pods.
+      # Specify `labels <https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/>` to associate to Tenant pods.
       labels: { }
-      ###
+      
       #
-      # An array of `Toleration labels <https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/>`__ to associate to Tenant pods.
+      # An array of `Toleration labels <https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/>` to associate to Tenant pods.
       #
       # These settings determine the distribution of pods across worker nodes.
       tolerations: [ ]
-      ###
+      
-      # Any `Node Selectors <https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/>`__ to apply to Tenant pods.
+      # Any `Node Selectors <https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/>` to apply to Tenant pods.
       #
       # The Kubernetes scheduler uses these selectors to determine which worker nodes onto which it can deploy Tenant pods.
       #
       # If no worker nodes match the specified selectors, the Tenant deployment will fail.
       nodeSelector: { }
-      ###
+      
       #
-      # The `affinity <https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/>`__ or anti-affinity settings to apply to Tenant pods.
+      # The `affinity <https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/>` or anti-affinity settings to apply to Tenant pods.
       #
       # These settings determine the distribution of pods across worker nodes and can help prevent or allow colocating pods onto the same worker nodes.
       affinity: { }
-      ###
+      
       # 
-      # The `Requests or Limits <https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/>`__ for resources to associate to Tenant pods.
+      # The `Requests or Limits <https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/>` for resources to associate to Tenant pods.
       #
       # These settings can control the minimum and maximum resources requested for each pod.
       # If no worker nodes can meet the specified requests, the Operator may fail to deploy.
       resources: { }
-      ###
+      
-      # The Kubernetes `SecurityContext <https://kubernetes.io/docs/tasks/configure-pod-container/security-context/>`__ to use for deploying Tenant resources.
+      # The Kubernetes `SecurityContext <https://kubernetes.io/docs/tasks/configure-pod-container/security-context/>` to use for deploying Tenant resources.
       #
       # You may need to modify these values to meet your cluster's security and access settings.
       #
@@ -158,8 +158,8 @@ tenant:
         fsGroup: 1000
         fsGroupChangePolicy: "OnRootMismatch"
         runAsNonRoot: true
-      ###
+      
-      # The Kubernetes `SecurityContext <https://kubernetes.io/docs/tasks/configure-pod-container/security-context/>`__ to use for deploying Tenant containers.
+      # The Kubernetes `SecurityContext <https://kubernetes.io/docs/tasks/configure-pod-container/security-context/>` to use for deploying Tenant containers.
       # You may need to modify these values to meet your cluster's security and access settings.
       containerSecurityContext:
         runAsUser: 1000
@@ -171,20 +171,20 @@ tenant:
             - ALL
         seccompProfile:
           type: RuntimeDefault
-      ###
+      
       #
-      # An array of `Topology Spread Constraints <https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/>`__ to associate to Operator Console pods.
+      # An array of `Topology Spread Constraints <https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/>` to associate to Operator Console pods.
       #
       # These settings determine the distribution of pods across worker nodes.
       topologySpreadConstraints: [ ]
-      ###
+      
       #
-      # The name of a custom `Container Runtime <https://kubernetes.io/docs/concepts/containers/runtime-class/>`__ to use for the Operator Console pods.
+      # 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::
@@ -193,62 +193,62 @@ 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>`__.
+    # 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>`__.
+    # 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.
+    #    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>`__
+    # 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>`__
+    # 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>`__.
+  # 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:
   # 
@@ -258,31 +258,31 @@ tenant:
   #         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.
+  # Each secret should specify the ``CONSOLEACCESSKEY`` and ``CONSOLESECRETKEY`` 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. 
+  # 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. 
+  # 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.
+  # `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. 
+  # `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.
+  # 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.
@@ -292,13 +292,13 @@ tenant:
   #
   # 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.
+  # 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.
@@ -312,24 +312,24 @@ tenant:
   #    $ 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.
+  # 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:
@@ -344,8 +344,8 @@ tenant:
   additionalVolumeMounts: [ ]
  
 
-###
+
-# Configures `Ingress <https://kubernetes.io/docs/concepts/services-networking/ingress/>`__ for the Tenant S3 API and Console.
+# 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:
@@ -385,5 +385,5 @@ ingress:
 #      name: {{ dig "tenant" "configSecret" "name" "" (.Values | merge (dict)) }}
 #    stringData:
 #      config.env: |-
-#        export MINIO_ROOT_USER='minio'
+#        export MINIOROOTUSER='minio'
-#        export MINIO_ROOT_PASSWORD='minio123'
+#        export MINIOROOTPASSWORD='minio123'