Prerequisites and limitations

Prerequisites and limitations for configuring Minio in your IBM® Cloud Private cluster.

Prerequisites

Ensure that the following configurations are complete in your cluster:

• Kubernetes 1.10 or higher with Beta APIs must be enabled.
• A secret object that contains access and secret keys that are in base64 encoded form must be available. For more information, see Minio .
• If you are configuring Minio in a distributed mode, you must configure block storage. This storage can be GlusterFS, Ceph, or any other Kubernetes supported storage provider. The block storage must be available through dynamic volume provisioning by using a storage class.
• If you are configuring Minio in a stand-alone mode, you can use emptyDir for data storage. However, when a pod is removed from a node, the data is permanently deleted. If you need data persistence, you configure block storage and use a storage class for dynamic volume provisioning.
• If you are deploying Minio in network-attached storage (NAS) gateway mode, you need a persistent volume (PV) running with ReadWriteMany supported volume plug-ins. For providers that support ReadWriteMany mode, see https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes.

Limitations

• Minio is supported only on Linux® x86_64 clusters.
• When you specify a clusterIP for the Minio service and TLS is enabled, the Minio service is not accessible by the service name or by the clusterIP.