Specify the total amount of memory (RAM) to allocate per MinIO server pod. The specified Storage Class must correspond to a set of Persistent Volumes sufficient in capacity to match each generated PVC. The Operator sets this value as the requested storage capacity in each generated PVC. The Operator displays the Drive Capacity under the:guilabel: Resource Allocation section. Specify both the total storage size and the Unit of that storage.Īll storage units are in SI values, e.g. The total raw storage size for the Tenant. The specified Storage Class must correspond to a set of Persistent Volumes sufficient in number to match each generated PVC. The Operator generates an equal number of PVC plus two for supporting Tenant services (Metrics and Log Search). The Operator displays the Total Volumes under the Resource Allocation section. The number of storage volumes (Persistent Volume Claims) the Operator requests per Server. Use the Pod Placement pane to modify the pod scheduling settings for the Tenant. The Operator by default uses pod anti-affinity, such that the Kubernetes cluster must have at least one worker node per MinIO server pod. The Operator enforces a minimum of four server pods per tenant. The total number of MinIO server pods to deploy in the Tenant. Specify the Kubernetes Storage Class the Operator uses when generating Persistent Volume Claims for the Tenant.Įnsure the specified storage class has sufficient available Persistent Volume resources to match each generated Persistent Volume Claim. The Operator supports at most one MinIO Tenant per namespace. You can create the namespace by selecting the plus + icon if it does not exist. The Kubernetes Namespace in which to deploy the tenant. Settings marked with an asterisk * are required: The Setup pane displays core configuration settings for the MinIO Tenant. Open your browser to the specified URL and enter the JWT Token into the login page.Ĭlick the + Create Tenant to start creating a MinIO Tenant. Kubectl get secret/console-sa-secret -n minio-operator -o json | jq -r '.data.token' | base64 -d To deploy a tenant from the MinIO Operator Console, complete the following steps in order:ġ2) Connect to the Tenant 1) Access the MinIO Operator Console Deploy a Tenant using the MinIO Operator Console MinIO’s consistency guarantees require the exclusive storage access that ReadWriteOnce provides.įor Kubernetes clusters where nodes have Direct Attached Storage, MinIO strongly recommends using the DirectPV CSI driver.ĭirectPV provides a distributed persistent volume manager that can discover, format, mount, schedule, and monitor drives across Kubernetes nodes.ĭirectPV addresses the limitations of manually provisioning and monitoring local persistent volumes. MinIO can use any Kubernetes Persistent Volume (PV) that supports the ReadWriteOnce access mode. The host machine must have access to a web browser application. This procedure assumes the host machine has kubectl installed and configured with access to the target Kubernetes cluster. The Kubernetes infrastructure and the kubectl CLI tool must have the same version of 1.19.0+. Starting with v4.0.0, the MinIO Operator requires Kubernetes 1.19.0 and later. The output should display the Operator version as 5.0.5. You can install the MinIO plugin using either the Kubernetes Krew plugin manager or manually by downloading and installing the plugin binary to your local host: See Deploy the MinIO Operator for complete documentation on deploying the MinIO Operator. This procedure assumes the latest stable Operator Kubernetes Operator and assumes the local host has a matching installation of The procedures on this page requires a valid installation of the MinIO Prerequisites MinIO Kubernetes Operator and Plugin While this documentation may provide guidance for configuring or deploying Kubernetes-related resources on a best-effort basis, it is not a replacement for the official Kubernetes Documentation. This documentation assumes familiarity with all referenced Kubernetes concepts, utilities, and procedures. Installing the MinIO Kubernetes Operator automatically installs and configures the Operator Console. The Operator Console provides a rich user interface for deploying and managing MinIO Tenants on Kubernetes infrastructure. You can use basic Kubernetes YAML resource definitions to deploy Single-Node Single-Drive and Single-Node Multi-Drive topologies for local testing and evaluation as necessary. The MinIO Operator supports only the Distributed (Multi-Node Multi-Drive) MinIO topology. This procedure documents deploying a MinIO Tenant onto a stock Kubernetes cluster using the MinIO Operator Console. Deploy a Tenant using the MinIO Operator Consoleĭeploy a MinIO Tenant using the Command Line
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |