1
0
mirror of https://github.com/minio/docs.git synced 2025-04-21 08:05:59 +03:00
docs/source/includes/eks/deploy-minio-on-elastic-kubernetes-service.rst
Andrea Longo 65e284f453
Helm deploy docs (#851)
Document how to deploy with a Helm chart, based on [How to install MinIO
Using Helm in
Kubernetes](https://github.com/cniackz/public/wiki/How-to-install-MinIO-Using-Helm-in-Kubernetes).

This addition maintains the existing plugin instructions as the primary
path, with Helm as a child page under that. That makes room for future
deploy options.

The existing `common-install-operator-kubectl-plugin-install.rst` is now
in two parts, to allow only including the second part in the Helm
instructions. Also promoted the Upgrade page to be a sibling to Deploy.

Many of the original instructions are environment setup that enable
installing the Helm charts, starting Operator, and creating a tenant.
That will vary by the user's environment, so omitted for docs.

Staged:

http://192.241.195.202:9000/staging/DOCS-798/k8s/html/operations/install-deploy-manage/deploy-operator-helm.html

Fixes https://github.com/minio/docs/issues/798
2023-06-05 17:45:58 -06:00

3.6 KiB

Deploy MinIO Operator on Amazon Elastic Kubernetes Service

minio

Table of Contents

Overview

Amazon® Elastic Kubernetes Service® <what-is-eks.html> (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 kubectl minio CLI tool, or by using kustomize for YAML-defined deployments <operator/tree/master/examples/kustomization>.

MinIO supports the following methods for installing the MinIO Operator onto your EKS (Elastic Kubernetes Service) clusters:

Through the AWS Marketplace <product/multicloud-elastic-kubernetes-service>

MinIO maintains an AWS Marketplace listing through which you can register your EKS cluster with . Any 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 the kubectl minio plugin. For instructions on deploying the MinIO Operator through the AWS Marketplace, see Deploy MinIO through EKS <product/multicloud-elastic-kubernetes-service/deploy>

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

Prerequisites

Existing EKS Cluster

This procedure assumes an existing EKS (Elastic Kubernetes Service) 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 EKS Cluster

Ensure your host machine has a kubectl installation compatible with the target EKS cluster. For guidance on connecting kubectl to EKS, see Creating or updating a kubeconfig file for an Amazon EKS cluster <eks/latest/userguide/create-kubeconfig.html>.

Your kubectl configuration must include authentication as a user with the correct permissions. MinIO provides an example IAM policy for Marketplace-based installations in the MinIO Operator github repository <marketplace/blob/master/eks/iam-policy.json>. You can use this policy as a baseline for manual Operator installations.

Procedure