Configuring Minio during IBM Cloud Private installation

Configure Minio when you install your IBM® Cloud Private cluster.

Complete these steps to configure Minio:

1. Enable Minio storage. Set storage-minio: enabled under the management services list in the /<installation_directory>/cluster/config.yaml file.

   management_services:
    istio: disabled
    vulnerability-advisor: disabled
    storage-glusterfs: disabled
    storage-minio: enabled
   

2. Add the following piece of code to the config.yaml file:

## storage-minio settings
storage-minio:
  image:
    repository: "{{ image_repo }}/minio"
  mcImage:
    repository: "{{ image_repo }}/minio-mc"
  mode: standalone
  accessKey: "admin"
  secretKey: "admin1234"
  minioAccessSercret: "minio-secret"
  configPath: "/root/.minio/"
  mountPath: "/export"
  replica: 4
  persistence:
    enabled: false
    useDynamicProvisioning: false
    storageClass: standard
    accessMode: ReadWriteOnce
    size: 10Gi
  service:
    type: ClusterIP
    clusterIP: None
    loadBalancerIP: None
    port: 9000
    nodePort: 31311
  ingress:
    enabled: false
    path: /
    hosts: ""
    tls: ""
  tls:
    enabled: false
    type: "selfsigned"
    minioTlsSercret: ""
  nodeSelector: ""
  tolerations: ""

Following are the descriptions of the parameters that are required for a simple configuration. For an advanced configuration, see the complete list of available parameters: https://github.com/IBM/charts/blob/095c63b5a8b8ca8a030e4a48cdef1e13df9615b1/stable/ibm-minio-objectstore/README.md .

• image.repository is the location of the image repository.
• mcImage.repository is the location of the client image repository.
• mode is the Minio server mode. Valid options are standalone or distributed.
• accessKey is the access key of the Minio server. The key must be 5 - 20 characters.
• secretKey is the secret key of the Minio server. The key must be 8 - 40 characters.
• minioAccessSercret is the name of the Kubernetes secret object. Note: You can configure this parameter only if you are configuring Minio after IBM Cloud Private is installed.
• configPath is the location of the default configuration file.
• mountPath is the default mount path for the persistent drive.
• replica is the number of Minio nodes. This parameter is applicable only to the Minio distributed mode. The value must be 4 - 32 nodes.
• persistence.enabled is to set whether persistent volume is used to store data.
• persistence.useDynamicProvisioning is to set whether the persistent volume claim (PVC) uses a storage class to bind the volume.
• persistence.storageClass is the name of the storage Class to bind the PVC. Specify a storage class name if you set the persistence.useDynamicProvisioning to true.
• persistence.accessMode sets the access mode. Valid options are ReadWriteOnce or ReadOnly.
• persistence.size is the size of the PVC to be created by using a storage class.
• service.type is the Kubernetes service type. Allowed values are ClusterIP, LoadBalancer, or NodePort.
• service.clusterIP is the Kubernetes service cluster IP address. The default cluster IP address is used if you set service:type parameter to ClusterIP. You can specify another IP address, if required.
• service.loadBalancerIP is the Kubernetes service load balancer IP address. The default load balancer IP address is used if you set service.type parameter to loadBalancer. You can specify another IP address, if required.
• service.port is the Kubernetes port on which the service is exposed. Default value is 9000.
• service.nodePort exposes the service on the IP address of the node at a static port. Default value is 31311.
• ingress.enabled enables ingress controller.
• ingress.path is the path of the ingress controller. Default value is /.
• ingress.hosts are host names that are accepted by the ingress controller. For example, ["chart-example1.local", "chart-example2.local"].
• ingress.tls is the TLS configuration of the ingress controller. For example, [{"secretName": "chart-example-tls", "hosts": ["chart-example.local", "chart-example.local"]}].
• tls.enabled enables Minio server with TLS certificates when set to true. Default value is false.
• tls.type is for specifying whether the chart must autogenerate a self-signed TLS certificate or use the one that you provide. If you are providing the certificate, you must create a secret that contains a private key, TLS certificate, and a certificate authority (CA) certificate. You provide the secret name in the tls.minioTlsSercret parameter. Allowed values are selfsigned or provided.
• tls.minioTlsSercret is the secret that you create and contains a private key (key private.key), TLS certificate (key public.crt), and a CA certificate (key ca.crt) to configure the Minio server with TLS certificates. You must create and specify the secret in the same namespace where you are deploying the chart. Use this parameter if you set tls.type to provided.
• nodeSelector is adding node labels for pod assignment. Add labels as {"key":"value"} pair. For example, {"role": "minio-node"}.
• tolerations are toleration labels for pod assignment. Add labels as {"key":"value"} pair. For example, [{"operator":"Equal"}, {"effect":"NoSchedule"}].