diff --git a/source/includes/common/common-minio-kes.rst b/source/includes/common/common-minio-kes.rst index 029065cf..7340792c 100644 --- a/source/includes/common/common-minio-kes.rst +++ b/source/includes/common/common-minio-kes.rst @@ -140,9 +140,6 @@ See the tutorials for :ref:`minio-snsd`, :ref:`minio-snmd`, or :ref:`minio-mnmd` # Sets the default KMS key for the backend and SSE-KMS/SSE-S3 Operations) MINIO_KMS_KES_KEY_NAME=minio-backend-default-key - # Optional, defines the name for the KES server enclave to use. - # MINIO_KMS_KES_ENCLAVE= - Replace ``HOSTNAME`` with the IP address or hostname of the KES server. If the MinIO server host machines cannot resolve or reach the specified ``HOSTNAME``, the deployment may return errors or fail to start. @@ -155,14 +152,6 @@ MinIO uses the :envvar:`MINIO_KMS_KES_KEY_NAME` key for the following cryptograp - Encrypting objects using :ref:`SSE-KMS ` if the request does not include a specific |EK|. - Encrypting objects using :ref:`SSE-S3 `. -MinIO uses the :envvar:`MINIO_KMS_KES_ENCLAVE` key to define the name of the KES enclave to use. - -- Replace ```` with the name of the :term:`enclave` to use. - If not defined, MinIO does not send any enclave information. - This may result in using the default enclave for stateful KES servers. - - A KES :term:`enclave` provides an isolated space for its associated keys separate from other enclaves on a stateful KES server. - .. end-kes-configuration-minio-desc .. start-kes-enable-sse-kms-desc @@ -288,4 +277,4 @@ KES does not accept any client requests until it completes validation of all spe - **Never** use the ``Play`` sandbox for production environments. -.. end-kes-play-sandbox-warning \ No newline at end of file +.. end-kes-play-sandbox-warning diff --git a/source/includes/container/common-minio-kes.rst b/source/includes/container/common-minio-kes.rst index 1331bb12..f35d5aec 100644 --- a/source/includes/container/common-minio-kes.rst +++ b/source/includes/container/common-minio-kes.rst @@ -103,7 +103,6 @@ This command assumes the ``minio-kes.cert``, ``minio-kes.key``, and ``kes-server MINIO_KMS_KES_KEY_FILE=/certs/minio-kes.key MINIO_KMS_KES_CAPATH=/certs/server.cert MINIO_KMS_KES_KEY_NAME=minio-backend-default-key - MINIO_KMS_KES_ENCLAVE= MinIO uses the :envvar:`MINIO_KMS_KES_KEY_NAME` key for the following cryptographic operations: @@ -111,14 +110,6 @@ MinIO uses the :envvar:`MINIO_KMS_KES_KEY_NAME` key for the following cryptograp - Encrypting objects using :ref:`SSE-KMS ` if the request does not include a specific |EK|. - Encrypting objects using :ref:`SSE-S3 `. -MinIO uses the :envvar:`MINIO_KMS_KES_ENCLAVE` key to define the name of the KES enclave to use. - -- Replace ```` with the name of the :term:`enclave` to use. -- If not defined, MinIO does not send any enclave information. - This may result in using the default enclave for stateful KES servers. - - A KES :term:`enclave` isolates its associated keys from other enclaves on a stateful KES server. - The ``minio-kes`` certificates enable for mTLS between the MinIO deployment and the KES server *only*. They do not otherwise enable TLS for other client connections to MinIO. diff --git a/source/includes/eks/deploy-minio-on-elastic-kubernetes-service.rst b/source/includes/eks/deploy-minio-on-elastic-kubernetes-service.rst index b7c7f1a5..0fbefc5d 100644 --- a/source/includes/eks/deploy-minio-on-elastic-kubernetes-service.rst +++ b/source/includes/eks/deploy-minio-on-elastic-kubernetes-service.rst @@ -14,7 +14,7 @@ Overview -------- :eks-docs:`Amazon® Elastic Kubernetes Service® ` (EKS) is an enterprise-ready Kubernetes container platform with full-stack automated operations to manage hybrid cloud, multi-cloud, and edge deployments. -The MinIO Kubernetes Operator supports deploying MinIO Tenants onto EKS infrastructure using the MinIO Operator Console, using the :mc:`kubectl minio` CLI tool, or by using `kustomize `__ for :minio-git:`YAML-defined deployments `. +The MinIO Kubernetes Operator supports deploying MinIO Tenants onto EKS infrastructure using the MinIO Operator Console or by using `kustomize `__ for :minio-git:`YAML-defined deployments `. MinIO supports the following methods for installing the MinIO Operator onto your :abbr:`EKS (Elastic Kubernetes Service)` clusters: diff --git a/source/includes/gke/deploy-minio-on-google-kubernetes-engine.rst b/source/includes/gke/deploy-minio-on-google-kubernetes-engine.rst index 38460014..2a0ecd2d 100644 --- a/source/includes/gke/deploy-minio-on-google-kubernetes-engine.rst +++ b/source/includes/gke/deploy-minio-on-google-kubernetes-engine.rst @@ -14,7 +14,7 @@ Overview -------- `Google Kubernetes Engine `__ (GKE) offers a highly automated secure and fully managed Kubernetes platform. -The MinIO Kubernetes Operator supports deploying MinIO Tenants onto GKE infrastructure using the MinIO Operator Console, the :mc:`kubectl minio` CLI tool, or `kustomize `__ for :minio-git:`YAML-defined deployments `. +The MinIO Kubernetes Operator supports deploying MinIO Tenants onto GKE infrastructure using the MinIO Operator Console or `kustomize `__ for :minio-git:`YAML-defined deployments `. :minio-web:`Through the GKE Marketplace ` MinIO maintains an `GKE Marketplace listing `__ through which you can register your GKE cluster with |subnet|. diff --git a/source/includes/windows/common-minio-kes.rst b/source/includes/windows/common-minio-kes.rst index 9dbcce3d..7e827449 100644 --- a/source/includes/windows/common-minio-kes.rst +++ b/source/includes/windows/common-minio-kes.rst @@ -102,7 +102,6 @@ This command assumes the ``minio-kes.cert``, ``minio-kes.key``, and ``kes-server MINIO_KMS_KES_KEY_FILE=|miniocertpath|\minio-kes.key MINIO_KMS_KES_CAPATH=|miniocertpath|\kes-server.cert MINIO_KMS_KES_KEY_NAME=minio-backend-default-key - MINIO_KMS_KES_ENCLAVE= MinIO uses the :envvar:`MINIO_KMS_KES_KEY_NAME` key for the following cryptographic operations: @@ -110,15 +109,7 @@ MinIO uses the :envvar:`MINIO_KMS_KES_KEY_NAME` key for the following cryptograp - Encrypting objects using :ref:`SSE-KMS ` if the request does not include a specific |EK|. - Encrypting objects using :ref:`SSE-S3 `. -MinIO uses the :envvar:`MINIO_KMS_KES_ENCLAVE` key to define the name of the KES enclave to use for stateful KES servers. - -- Replace ```` with the name of the :term:`enclave` to use. -- If not defined, MinIO does not send any enclave information. - This may result in using the default enclave for stateful KES servers. - - A KES :term:`enclave` provides an isolated space for its associated keys separate from other enclaves on a stateful KES server. - The ``minio-kes`` certificates enable mTLS between the MinIO deployment and the KES server *only*. They do not otherwise enable TLS for other client connections to MinIO. -.. end-kes-configuration-minio-desc \ No newline at end of file +.. end-kes-configuration-minio-desc diff --git a/source/url-excludes.yaml b/source/url-excludes.yaml index 6a8440d5..78374cff 100644 --- a/source/url-excludes.yaml +++ b/source/url-excludes.yaml @@ -155,6 +155,7 @@ excludes: - 'operations/install-deploy-manage/deploy-minio-single-node-single-drive.rst' - 'operations/install-deploy-manage/deploy-minio-single-node-multi-drive.rst' - 'operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst' +- 'operations/install-deploy-manage/deploy-operator-helm.rst' - 'operations/install-deploy-manage/upgrade-minio-deployment.rst' - 'operations/install-deploy-manage/expand-minio-deployment.rst' - 'operations/install-deploy-manage/decommission-server-pool.rst' @@ -172,6 +173,7 @@ excludes: - 'operations/install-deploy-manage/deploy-minio-single-node-single-drive.rst' - 'operations/install-deploy-manage/deploy-minio-single-node-multi-drive.rst' - 'operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst' +- 'operations/install-deploy-manage/deploy-operator-helm.rst' - 'operations/install-deploy-manage/upgrade-minio-deployment.rst' - 'operations/install-deploy-manage/expand-minio-deployment.rst' - 'operations/install-deploy-manage/decommission-server-pool.rst' @@ -189,6 +191,7 @@ excludes: - 'operations/install-deploy-manage/deploy-minio-single-node-single-drive.rst' - 'operations/install-deploy-manage/deploy-minio-single-node-multi-drive.rst' - 'operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst' +- 'operations/install-deploy-manage/deploy-operator-helm.rst' - 'operations/install-deploy-manage/upgrade-minio-deployment.rst' - 'operations/install-deploy-manage/expand-minio-deployment.rst' - 'operations/install-deploy-manage/decommission-server-pool.rst' @@ -206,6 +209,7 @@ excludes: - 'operations/install-deploy-manage/deploy-minio-single-node-single-drive.rst' - 'operations/install-deploy-manage/deploy-minio-single-node-multi-drive.rst' - 'operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.rst' +- 'operations/install-deploy-manage/deploy-operator-helm.rst' - 'operations/install-deploy-manage/upgrade-minio-deployment.rst' - 'operations/install-deploy-manage/expand-minio-deployment.rst' - 'operations/install-deploy-manage/decommission-server-pool.rst'