"GitOps" and "Databases" have historically been enemies. While stateless microservices are easy to manage with ArgoCD or Flux, upgrading a multi-node OpenSearch cluster via Git commits often strikes fear into the heart of Platform Engineers. Will the PVCs reattach? Will the shards rebalance correctly? Or will we suffer a split-brain scenario?

This session bridges the gap between the OpenSearch Operator and GitOps principles. We will move beyond the basic Helm install and architect a robust, self-healing OpenSearch stack running on Kubernetes.

We will cover:

The Operator Pattern: Why using the OpenSearch K8s Operator is non-negotiable for Day-2 operations (upgrades, scaling, and certificate rotation).

GitOps Workflows: How to structure your ArgoCD/Flux manifests to manage index policies and user roles as code, ensuring your search infrastructure is as reproducible as your application code.

Disaster Recovery: A live look at how to handle "StatefulSet" roadblocks when a node goes down, and how to perform automated snapshots to S3 using the Snapshot Management policy.