minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-28 19:42:10 +03:00
Code Activity

Operator sidecar (#838)

Browse Source 
This adds information about Operator component changes in v5.0.x.

Closes #791 

Staged:
http://192.241.195.202:9000/staging/operator-sidecar/operations/installation.html
This commit is contained in:
Daryl White
2023-05-05 10:39:13 -05:00
committed by GitHub
parent dbb34f4b3e
commit 48d78340ff
6 changed files with 151 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
source/operations/install-deploy-manage/minio-operator-console.rst
View File

@ -43,7 +43,12 @@ The MinIO Operator Console supports deploying, managing, and monitoring MinIO Te
You can :ref:`deploy a MinIO Tenant <minio-k8s-deploy-minio-tenant>` through the Operator Console.
The Operator Console automatically detects MinIO Tenants deployed on the cluster when provisioned through the Operator Console, the :ref:`MinIO Kubernetes Plugin <minio-k8s-deploy-minio-tenant-commandline>`, Helm, or Kustomize.
The Operator Console automatically detects MinIO Tenants deployed on the cluster when provisioned through:
- Operator Console
- :ref:`MinIO Kubernetes Plugin <minio-k8s-deploy-minio-tenant-commandline>`
- Helm
- Kustomize
Select a listed tenant to open an in-browser view of that tenant's MinIO Console.
You can use this view to directly manage, modify, expand, upgrade, and delete the tenant through the Operator UI.
@ -56,12 +61,12 @@ You can use this view to directly manage, modify, expand, upgrade, and delete th
The ZIP archive contains status, events, and log information for each pool on the deployment.
The archive also includes a summary yaml file describing the deployment.
|subnet| users can upload this file for analysis by MinIO Engineers.
|subnet| users relying on the commercial license should register the MinIO tenants to their SUBNET account, which can be done through the Operator Console.
Tenant Registration
-------------------
|subnet| users relying on the commercial license should register your MinIO tenants to your SUBNET account, which can be done through the Operator Console.
|subnet| users relying on the commercial license should register the MinIO tenants to their SUBNET account, which can be done through the Operator Console.
.. image:: /images/k8s/operator-console-register.png
:align: center

4
source/operations/install-deploy-manage/upgrade-minio-operator.rst
View File

@ -65,7 +65,7 @@ The following changes apply for Operator v5.0.0 or later:
This change impacts the Tenant :abbr:`CRD <CustomResourceDefinition>` and only impacts users editing a tenant YAML directly, such as through Helm or Kustomize.
- Both the **Log Search API** (``.spec.log``) and **Prometheus** (``.spec.prometheus``) deployments have been removed.
However, existing deployments are left running as standalone deployments / statefulsets with no connection to the Tenant CR.
If the Tenant CRD is deleted, this does not cascade to the log or Prometheus deployments.
Deleting the Tenant :abbr:`CRD (Custom Resource Definition)` does **not** cascade to the log or Prometheus deployments.
.. important::
@ -170,7 +170,7 @@ Upgrade Operator to |operator-version-stable|
"name": "minio-operator"
}
3. Download the Latest Stable Version of the MinIO Kubernetes Plugin
3. Download the latest stable version of the MinIO Kubernetes Plugin
.. include:: /includes/k8s/install-minio-kubectl-plugin.rst