3.0 KiB
1) Install the MinIO Kubernetes Plugin
The MinIO Kubernetes Plugin provides a command for initializing the MinIO Operator.
2) Initialize the MinIO Kubernetes Operator
Run the kubectl minio init
command to initialize the MinIO
Operator:
kubectl minio init
The command initializes the MinIO Operator with the following default settings:
- Deploy the Operator into the
minio-operator
namespace. Specify thekubectl minio init --namespace
argument to deploy the operator into a different namespace. - Use
cluster.local
as the cluster domain when configuring the DNS hostname of the operator. Specify thekubectl minio init --cluster-domain
argument to set a differentcluster domain <tasks/administer-cluster/dns-custom-nameservers/>
value.
Important
Document all arguments used when initializing the MinIO Operator.
3) Validate the Operator Installation
To verify the installation, run the following command:
kubectl get all --namespace minio-operator
If you initialized the Operator with a custom namespace, replace
minio-operator
with that namespace.
The output resembles the following:
NAME READY STATUS RESTARTS AGE
pod/console-59b769c486-cv7zv 1/1 Running 0 81m
pod/minio-operator-7976b4df5b-rsskl 1/1 Running 0 81m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/console ClusterIP 10.105.218.94 <none> 9090/TCP,9443/TCP 81m
service/operator ClusterIP 10.110.113.146 <none> 4222/TCP,4233/TCP 81m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/console 1/1 1 1 81m
deployment.apps/minio-operator 1/1 1 1 81m
NAME DESIRED CURRENT READY AGE
replicaset.apps/console-59b769c486 1 1 1 81m
replicaset.apps/minio-operator-7976b4df5b 1 1 1 81m
4) Open the Operator Console
Run the kubectl minio proxy
command to temporarily forward
traffic from the MinIO Operator Console <minio-operator-console>
service to your local machine:
kubectl minio proxy
The command output includes a JWT token you must use to log into the Operator Console.
You can deploy a new MinIO Tenant <minio-k8s-deploy-minio-tenant>
from the Operator Dashboard.