For the complete documentation index, see llms.txt. This page is also available as Markdown.

WEKA Operator deployments

Deploy WEKA on Kubernetes with the WEKA Operator. Choose the deployment model that fits your environment, verify version support, and continue to the right workflow.

WEKA Operator capabilities

The WEKA Operator automates the deployment and lifecycle management of WEKA storage on Kubernetes. It manages the full stack through Kubernetes-native custom resources, removing the need for manual coordination across cluster components.

The Operator handles the following:

  • Resource provisioning: Deploys and manages WekaCluster and WekaClient custom resources as Kubernetes-native objects.

  • Driver lifecycle: Distributes pre-built drivers and supports local driver build workflows for custom or restricted environments.

  • CSI management: Embeds and manages the WEKA CSI Plugin lifecycle as part of the WekaClient resource.

  • Observability and monitoring: Exposes WEKA health and performance metrics to Kubernetes monitoring stacks.

  • Protocol gateways: Manages protocol containers, including S3, NFS, SMB, and audit, from the WekaCluster resource.

  • Drive sharing and composable backends: Supports drive sharing configuration, drive type ratios, and capacity-based backend layouts.

  • Upgrade management: Supports rolling, manual, and all-at-once upgrade policies for client pods.

  • Cluster maintenance controls: Supports CSI migration, cluster pause and resume, and cluster deletion cancellation.

The WEKA Operator is updated frequently. For the latest feature additions and changes, always refer to the release notes for your target Operator version before deployment or upgrade. For example: WEKA Operator 1.14.0 release notes.

Deployment models

Choose the model that matches your infrastructure and operating boundary.

Full deployment on Kubernetes: Run WEKA backend and client processes in Kubernetes. Use this model when Kubernetes hosts both the WEKA data plane and application workloads.

Client-only deployment: Run WEKA clients in Kubernetes and connect them to a WEKA cluster running outside Kubernetes. Use this model when the storage cluster already runs on dedicated servers.

Managed Kubernetes services: Run supported WEKA components on Amazon EKS, Oracle OKE, Google GKE, or Azure AKS. Platform support and deployment limits vary by provider and instance type.

Version compatibility

Verify minimum version requirements before deployment or upgrade.

Feature
Operator (min. version)
WEKA Cluster (min. version)
Notes

S3

1.7

4.4

Supported.

NFS

1.10

5.1.0

Supported.

Audit

1.10

5.1.0

Supported.

SMB-W

1.11

5.1.20

Supported.

Data Services

1.13

5.1.20

Supported for quota coloring. Not supported for Data Catalog.

ssdproxy

1.12

5.1.30

Supported. Share NVMe drives across multiple clusters.

AlloyFlash

1.14

5.1.30

Supported. Enable mixed TLC and QLC drive deployments.

Cluster capacity sizing

1.14.2

5.1.0

Supported. Size the cluster by target usable capacity with dynamicTemplate.clusterCapacity.

How to use this guide

Use this guide to choose the right starting point for deployment and operations tasks.

Concept topics and references:

WEKA Operator architecture overview

WEKA CRD API Reference

WekaCluster and WekaContainer lifecycle

Kubernetes deployment types

Start a new deployment:

Task
Topic

Generate deployment artifacts with a guided wizard (recommended for common deployments)

Minimal working cluster in five steps

Full deployment workflow end-to-end

Deploy on a cloud-managed Kubernetes service

Go to a specific task: Use these topics for focused configuration and migration work.

Operate and maintain after deployment: Use these topics to upgrade, optimize, and troubleshoot the environment.

Task
Topic

Monitor, scale, and maintain the cluster

Plan a WEKA version upgrade

Production guidance

Last updated