MinIO supports Transport Layer Security (TLS) 1.2+ encryption of incoming and outgoing traffic.
SSL is Deprecated
TLS is the successor to Secure Socket Layer (SSL) encryption. SSL is fully deprecated as of June 30th, 2018.
For Kubernetes clusters with a valid TLS Cluster Signing Certificate, the MinIO Kubernetes Operator can automatically generate TLS certificates while deploying or modifying a MinIO Tenant. The TLS certificate generation process is as follows:
The Operator generates a Certificate Signing Request (CSR) associated to the Tenant. The CSR includes the appropriate DNS Subject Alternate Names (SANs) for the Tenant services and pods.
The Operator then waits for CSR approval
The CSR waits pending approval. The Kubernetes TLS API can automatically approve the CSR if properly configured. Otherwise, a cluster administrator must manually approve the CSR before Kubernetes can generate the necessary certificates.
The Operator applies the generated TLS Certificates to each MinIO Pod in the Tenant.
The Kubernetes TLS API uses the Kubernetes cluster Certificate Authority (CA) signature algorithm when generating new TLS certificates. See Supported TLS Cipher Suites for a complete list of MinIO’s supported TLS Cipher Suites and recommended signature algorithms.
By default, Kubernetes places a certificate bundle on each pod at
This CA bundle should include the cluster or root CA used to sign the MinIO Tenant TLS certificates.
Other applications deployed within the Kubernetes cluster can trust this cluster certificate to connect to a MinIO Tenant using the MinIO service DNS name (e.g.
Subject Alternative Name Certificates
If you have a custom Subject Alternative Name (SAN) certificate that is not also a wildcard cert, the TLS certificate SAN must apply to the hostname for its parent node. Without a wildcard, the SAN must match exactly to be able to connect to the tenant.
MinIO supports three types of secrets in Kubernetes.
cert-manager 1.7.x or later
Running on Kubernetes 1.21 or later.
For the best support of tls or cert-manager secrets, upgrade to Operator version 5.0.10 or later.
These custom certificates support Server Name Indication (SNI), where the MinIO server identifies which certificate to use based on the hostname specified by the connecting client. For example, you can generate certificates signed by your organization’s preferred Certificate Authority (CA) and attach those to the MinIO Tenant. Applications which trust that CA can connect to the MinIO Tenant and fully validate the Tenant TLS certificates.
MinIO supports the following TLS 1.2 and 1.3 cipher suites as supported by Go. The lists mark recommended algorithms with a icon:
If deploying MinIO Tenants with certificates minted by a non-global or non-public Certificate Authority, or if using a global CA that requires the use of intermediate certificates, you must provide those CAs to the Operator to ensure it can trust those certificates.
The Operator may log warnings related to TLS cert validation for Tenants deployed with untrusted certificates.
The following procedure attaches a secret containing the
public.crt of the Certificate Authority to the MinIO Operator.
You can specify multiple CAs in a single certificate, as long as you maintain the
END delimiters as-is.
The following creates a Kubernetes secret in the MinIO Operator namespace (
kubectl create secret generic operator-ca-tls \ --from-file=public.crt -n minio-operator
public.crtfile must correspond to a valid TLS certificate containing one or more CA definitions.
Restart the Operator
Once created, you must restart the Operator to load the new CAs:
kubectl rollout restart deployments.apps/minio-operator -n minio-operator