cert-manager for Operator
MinIO Operator manages TLS certificate issuing for the services hosted in the minio-operator namespace.
This page describes how to manage the Operator’s TLS certificates with cert-manager.
Prerequisites
kustomize installed
kubectlaccess to yourk8sclusterCompleted the steps to set up cert-manager
The MinIO Operator must not yet be installed.
1) Create a CA Issuer for the minio-operator namespace
This guide disables the automatic generation of certificates in MinIO Operator and issues certificates using cert-manager instead.
The minio-operator namespace must have its own certificate authority (CA), derived from the cluster’s ClusterIssuer certificate created during cert-manager setup.
Create this CA certificate using cert-manager.
Important
This CA certificate must exist before installing MinIO Operator.
If it does not exist, create the
minio-operatornamespacekubectl create ns minio-operator
Request a new Certificate with
spec.isCA: truespecified.This certificate serves as the CA for the minio-operator namespace.
Create a file called
operator-ca-tls-secret.yamlwith the following contents:# operator-ca-tls-secret.yaml apiVersion: cert-manager.io/v1 kind: Certificate metadata: name: minio-operator-ca-certificate namespace: minio-operator spec: isCA: true commonName: operator secretName: operator-ca-tls duration: 70128h # 8y privateKey: algorithm: ECDSA size: 256 issuerRef: name: selfsigned-root kind: ClusterIssuer group: cert-manager.io
Important
The
spec.issueRef.namemust match the name of theClusterIssuercreated when setting up cert-manager. If you specified a differentClusterIssuername or are using a differentIssuerfrom the guide, modify theissuerRefto match your environment.Apply the resource:
kubectl apply -f operator-ca-tls-secret.yaml
Kubernetes creates a new secret with the name operator-ca-tls in the minio-operator namespace.
Important
Make sure to trust this certificate in any applications that need to interact with the MinIO Operator.
2) Use the secret to create the Issuer
Use the operator-ca-tls secret to add an Issuer resource for the minio-operator namespace.
Create a file called
operator-ca-issuer.yamlwith the following contents:# operator-ca-issuer.yaml apiVersion: cert-manager.io/v1 kind: Issuer metadata: name: minio-operator-ca-issuer namespace: minio-operator spec: ca: secretName: operator-ca-tls
Apply the resource:
kubectl apply -f operator-ca-issuer.yaml
3) Create TLS certificate
Now that the Issuer exists in the minio-operator namespace, cert-manager can add a certificate.
The certificate from cert-manager must be valid for the following DNS domains:
stssts.minio-operator.svc.sts.minio-operator.svc.<cluster domain>Important
Replace
<cluster domain>with the actual value for your MinIO tenant.cluster domainis the internal root DNS domain assigned in your Kubernetes cluster. Typically, this iscluster.local, but confirm the value by checking your CoreDNS configuration for the correct value for your Kubernetes cluster.For example:
kubectl get configmap coredns -n kube-system -o jsonpath="{.data}"
Different Kubernetes providers manage the root domain differently. Check with your Kubernetes provider for more information.
Create a
Certificatefor the specified domains:Create a file named
sts-tls-certificate.yamlwith the following contents:# sts-tls-certificate.yaml apiVersion: cert-manager.io/v1 kind: Certificate metadata: name: sts-certmanager-cert namespace: minio-operator spec: dnsNames: - sts - sts.minio-operator.svc - sts.minio-operator.svc.cluster.local # Replace cluster.local with the value for your domain. secretName: sts-tls issuerRef: name: minio-operator-ca-issuer
Important
The
spec.secretNameis not optional.The secret name must be
sts-tls. Confirm this by settingspec.secretName: sts-tlsas highlighted in the certificate YAML.Apply the resource:
kubectl apply -f sts-tls-certificate.yaml
This creates a secret called sts-tls in the minio-operator namespace.
Warning
The STS service will not start if the sts-tls secret, containing the TLS certificate, is missing or contains an invalid key-value pair.
4) Install Operator with Auto TLS disabled
You can now install the MinIO Operator.
When installing the Operator deployment, set the OPERATOR_STS_AUTO_TLS_ENABLED environment variable to off in the minio-operator container.
Disabling this environment variable prevents the MinIO Operator from issuing the certificates. Instead, Operator relies on cert-manager to issue the TLS certificate.
There are various methods to define an environment variable depending on how you install the Operator. The following steps define the variable with kustomize.
Create a kustomization patch file called
kustomization.yamlwith the following contents:# minio-operator/kustomization.yaml apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: - github.com/minio/operator/resources patches: - patch: |- apiVersion: apps/v1 kind: Deployment metadata: name: minio-operator namespace: minio-operator spec: template: spec: containers: - name: minio-operator env: - name: OPERATOR_STS_AUTO_TLS_ENABLED value: "off" - name: OPERATOR_STS_ENABLED value: "on"
Apply the kustomization resource to the cluster:
kubectl apply -k minio-operator
Migrate an existing MinIO Operator deployment to cert-manager
To transition an existing MinIO Operator deployment from using AutoCert to cert-manager, complete the following steps:
Complete the steps for installing cert-manager, including disabling auto-cert.
Complete steps 1-3 on this page to generate the certificate authority for the Operator.
When you get to the install step on this page, instead replace the existing Operator TLS certificate with the cert-manager issued certificate.
Create new cert-manager certificates for each tenant, similar to the steps described on the cert-manager for Tenants page.
Replace the secrets in the MinIO Operator namespace for the tenants with secrets related to each tenant’s cert-manager issued certificate.
Next steps
Set up cert-manager for a MinIO Tenant.