minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-05-29 12:01:29 +03:00
Code
docs/source/includes/aks/deploy-minio-on-azure-kubernetes-service.rst
Andrea Longo b173e7bb6e
Fix build warnings for Operator pages (#1238) 
Fix build warnings from https://github.com/minio/docs/pull/1219 

Some are broken refs that need to point elsewhere.

Some are because `openshift`, `eks`, `gke`, `aks` can't see a target
that's on a `k8s` page, apparently due to how
`operations/installation.rst` is structured. These we are still
investigating.
2024-06-07 13:37:24 -06:00

2.9 KiB
Raw Blame History

Deploy MinIO Operator on Azure Kubernetes Service

minio

Table of Contents

Overview

Azure Kubernetes Engine (AKS) is a highly available, secure, and fully managed Kubernetes service from Microsoft Azure. The MinIO Kubernetes Operator supports deploying MinIO Tenants onto AKS infrastructure using the MinIO Operator Console or kustomize for YAML-defined deployments <operator/tree/master/examples/kustomization>.

Through the AKS Marketplace <product/multicloud-azure-kubernetes-service>

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

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

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

Prerequisites

Existing AKS Cluster

This procedure assumes an existing AKS (Azure 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 AKS 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 AKS Cluster

Ensure your host machine has a kubectl installation compatible with the target AKS cluster. For guidance on connecting kubectl to AKS, see Install kubectl and configure cluster access <tutorial-kubernetes-deploy-cluster?tabs=azure-cli#connect-to-cluster-using-kubectl>.

Procedure

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