Managing YugabyteDB Schemas with the Atlas Kubernetes Operator
Teams don't adopt YugabyteDB by accident. They choose it when a single relational database primary can no longer keep up with their writes from payments, order processing, inventory, etc.
A distributed database carries more than just columns and types: every table and index records how data is split across the cluster, and those choices determine how the database performs at scale. Many teams run YugabyteDB next to their services on Kubernetes, where every other part of the system is versioned in a repository, reviewed in a pull request, and deployed by changing a manifest. A change to how a table is split deserves the same review as a change to its columns, and the same rollout to every cluster.
On YugabyteDB, Atlas models colocation, tablet pre-splitting, and index sharding as part of the schema, so the distribution layout is versioned, diffed, and deployed with the rest of it, instead of living in handwritten DDL that drifts between clusters. The Atlas Kubernetes Operator completes the picture: it applies each version of the migration directory to the database from a Kubernetes resource, the same way the cluster deploys a new image.
This post walks through how an application team can use Atlas and the Operator to declare, review, and evolve their distributed YugabyteDB schema.
