KubeDB

By AppsCode

github-icon twitterx-icon

GitOps-First Database Automation

Automate Database
Operations with
True GitOps

The only Kubernetes-native DBaaS that brings full GitOps
maturity to stateful workloads — at Operator Capability
Level 5

Best with:
KubeDB Operator
See GitOps in Action Schedule Demo

Level 5

GitOps Maturity

25+

Databases Supported

Zero

Reconciliation Conflicts

100%

Argo/Flux Compatible

The GitOps Challenge for Databases

Traditional database operators break GitOps

01

Spec Override Wars

GitOps tools keep reverting your manual changes because the operator mutates the CR spec.

02

Lost Hotfixes

Emergency fixes applied with kubectl disappear on next reconciliation.

03

No Audit Trail

Changes made outside Git violate the single source of truth principle.

Reconciliation Conflict

> kubectl scale postgres prod --replicas=5
> Argo CD detects drift...
> Reverts back to 3 replicas

Result: Endless fights. Downtime risk. Frustration.

KubeDB GitOps Solution

One Git commit.
Zero reconciliation pain.

postgres-gitops.yaml
Git
apiVersion: gitops.kubedb.com/v1alpha1
kind: PostgresGitOps
metadata:
  name: prod-db
spec:
  version: "16.4"
  replicas: 5
  storage:
    size: "200Gi"
  resources:
    requests:
      cpu: "4"
      memory: "16Gi"
  config: 
    max_connections: 500
  tls:
    enabled: true
1

Commit to Git

Push your desired database state using dedicated GitOps CRDs.

2

Argo CD / Flux Syncs

Your favorite GitOps tool applies the change safely.

OpsRequest Magic

KubeDB translates your declaration into safe, auditable OpsRequests — no spec fights.

Avoiding the Classic Operator Reconciliation Conflict

A common pain point with GitOps and most database operators

The Spec Override Problem

1
Declare desired state in Custom Resource spec
2
Operator reconciles, injecting defaults & optimizations
3
GitOps detects drift and attempts to revert
4
Endless reconciliation fights & failed syncs

Result: Endless reconciliation fights, failed syncs, noisy alerts, and operational instability

KubeDB's Solution

Manage everything via *.GitOps Custom Resource
GitOps operator watches this resource
Creates appropriate OpsRequest(s) for changes
Safe execution without spec conflicts

Result: Clean separation, no spec fights, auditable operations, single source of truth in Git

GitOps Features

Built from the ground up for declarative infrastructure

Declarative Everything

Define your entire database infrastructure as code in Git. Every change, from initial provisioning to day-2 operations, is tracked and version-controlled.

Conflict-Free Reconciliation

Dedicated GitOps CRDs eliminate the classic spec override problem. No more endless reconciliation fights between GitOps tools and operators.

OpsRequest Intelligence

Long-running operations are safely translated into controlled OpsRequests with validation, sequencing, progress tracking, and rollback support.

Production-Grade Safety

All changes go through intelligent merging, prerequisite validation, and safe execution paths. No direct mutations of critical database resources.

Why KubeDB Is the Only True GitOps-Ready Kubernetes-Native DBaaS

Broad Database Support

Consistent GitOps experience across 25+ databases including PostgreSQL, MySQL, MongoDB, Redis, Elasticsearch, Kafka, ClickHouse, and more.

OpsRequest Abstraction

Any change is safely translated into controlled, long-running operations with full auditability and rollback capabilities.

Conflict-Free by Design

GitOps CRDs eliminate the classic spec override problem that plagues traditional database operators.

Production-Grade Features

High availability, automated backup/restore via KubeStash, monitoring, TLS, encryption-at-rest, and full Level 5 Auto Pilot behaviors.

Native Integration

Works seamlessly with Argo CD, Flux, and any CNCF-aligned GitOps tooling without proprietary lock-in.

Single Source of Truth

Git-declared GitOps resources remain the authoritative source while the operator manages operational complexity behind the scenes.

Most other database operators either lack this level of GitOps maturity or force teams into imperative workarounds for day-2 operations.

GitOps-First Database Automation

Ship Database Changes Like Application Code

The only Level 5 operator with true GitOps maturity for databases

  • Declarative database lifecycle
  • No spec override conflicts
  • Full Argo/Flux compatibility
Start Free Trial Watch Demo
Level 5
Operator
100%
GitOps Ready
25+
Databases
10K+
Active DBs