mirror of
https://github.com/minio/docs.git
synced 2025-04-25 17:22:39 +03:00
94d1faa9c1
As per https://github.com/minio/console/issues/2539 , the websocket behavior integrated as part of Console 0.22.1 (https://github.com/minio/console/pull/2419) seems to break port-forwarding behavior. There's no easy fix for this. NodePorts are a workaround, but slightly kludgy. Ingress is the better long-term solution, but requires more work. This is a stopgap: - For Operator, point users towards NodePorts if port-forwarding fails - For Tenant Console, simply drop port-forwarding entirely and point only at Ingress/LB Out of scope but in progress is Ingress guidance for Nginx and Traefik so we can close the loop on this.
74 lines
2.5 KiB
ReStructuredText
74 lines
2.5 KiB
ReStructuredText
1) Install the MinIO Kubernetes Plugin
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
The MinIO Kubernetes Plugin provides a command for initializing the MinIO Operator.
|
|
|
|
.. include:: /includes/k8s/install-minio-kubectl-plugin.rst
|
|
|
|
2) Initialize the MinIO Kubernetes Operator
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Run the :mc:`kubectl minio init` command to initialize the MinIO Operator:
|
|
|
|
.. code-block:: shell
|
|
:class: copyable
|
|
|
|
kubectl minio init
|
|
|
|
The command initializes the MinIO Operator with the following default settings:
|
|
|
|
- Deploy the Operator into the ``minio-operator`` namespace.
|
|
Specify the :mc-cmd:`kubectl 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 the
|
|
:mc-cmd:`kubectl minio init --cluster-domain` argument to set a
|
|
different :kube-docs:`cluster 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:
|
|
|
|
.. code-block:: shell
|
|
:class: copyable
|
|
|
|
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:
|
|
|
|
.. code-block:: shell
|
|
|
|
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
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
.. include:: /includes/common/common-k8s-connect-operator-console.rst
|
|
|
|
|
|
|