minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-04-21 08:05:59 +03:00
Code
docs/source/includes/gke/deploy-minio-on-google-kubernetes-engine.rst
Andrea Longo c30bdaec84
fix additional build warnings (#1239) 
Fix more build warnings. This includes removing references to
`MINIO_KMS_KES_ENCLAVE`
2024-06-07 14:32:07 -06:00

3.1 KiB
Raw Permalink Blame History

Deploy MinIO Operator on Google Kubernetes Engine

minio

Table of Contents

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 or kustomize for YAML-defined deployments <operator/tree/master/examples/kustomization>.

Through the GKE Marketplace <product/multicloud-google-kubernetes-service>

MinIO maintains an GKE Marketplace listing through which you can register your GKE cluster with . Any MinIO tenant you deploy through Marketplace-connected clusters can take advantage of SUBNET registration, including 24/7 direct access to MinIO engineers.

Using the MinIO kubectl Plugin

MinIO provides a kubectl plugin for installing and managing the MinIO Operator and Tenants through a terminal or shell (CLI) environment. You can manually register these tenants with at any time.

This page documents deploying the MinIO Operator through the CLI using Kustomize. For instructions on deploying the MinIO Operator through the GKE Marketplace, see Deploy MinIO through GKE <product/multicloud-google-kubernetes-service/deploy>

This documentation assumes familiarity with all referenced Kubernetes and Google Kubernetes Engine concepts, utilities, and procedures. While this documentation may provide guidance for configuring or deploying Kubernetes-related or Google Kubernetes Engine-related resources on a best-effort basis, it is not a replacement for the official Kubernetes Documentation <>.

Prerequisites

Existing GKE Cluster

This procedure assumes an existing GKE (Google Kubernetes Engine) cluster onto which you can deploy the MinIO Operator.

The Operator by default deploys pods and services with two replicas each and pod anti-affinity. The GKE cluster should therefore have at least two nodes available for scheduling Operator pods and services. While these nodes may be the same nodes intended for use by MinIO Tenants, co-locating Operator and Tenant pods may increase the risk of service interruptions due to the loss of any one node.

kubectl Access to the GKE Cluster

Ensure your host machine has a kubectl installation compatible with the target GKE cluster. For guidance on connecting kubectl to GKE, see Install kubectl and configure cluster access <how-to/cluster-access-for-kubectl>.

Procedure

The following steps deploy Operator using Kustomize and a kustomization.yaml file from the MinIO Operator GitHub repository.