Lynq - Infrastructure as Data for Kubernetes

3 min read Original article ↗

A RecordOps platform that turns database records into infrastructure.
No YAML. No CI/CD delays. Just data.

MySQL

DatabaseMySQL Records

Lynq

LynqOperator

Kubernetes

KubernetesResources

Deploy

Service

Ingress

Secret

Why Teams Choose Lynq

Lynq is a RecordOps platform that implements Infrastructure as Data. Your database records become infrastructure specifications. Insert a row, provision a stack. Update a field, reconfigure resources. Delete a record, clean up everything.

Manual Provisioning ~30 minutes Lynq Automation ~30 seconds

Traditional GitOps GitCICDK8s Lynq Direct DBK8s

Manual Scripts DriftConflictDeps Lynq Automation

See It in Real-Time

Watch how a simple database change instantly triggers infrastructure updates across your Kubernetes cluster

Want to understand the architecture? Learn how LynqHub, LynqForm, and LynqNode work together to enable RecordOps.

Start in 5 minutes

Follow the Quick Start Guide to see this in action with a working MySQL database and sample templates.

Try It Now — No Setup Required

🎮

Interactive Playground

Experience Lynq hands-on in our browser-based Kubernetes environment. Add tenants, watch resources appear, and see automated cleanup — all in 10 minutes.

Launch Interactive Demo

Powered by Killercoda • Free to use

Fine-Grained Control with Policies

Customize resource lifecycle behavior with powerful policies for creation, deletion, and conflict resolution. Try the interactive simulators to see how each policy works in real-time.

🔄 Creation Policies

Control when resources are applied: Once for immutable resources like init Jobs, or WhenNeeded for dynamic updates

🗑️ Deletion Policies

Choose cleanup behavior: Delete to remove resources automatically, or Retain to preserve them after node deletion

⚠️ Conflict Policies

Handle ownership conflicts: Stuck to prevent overwrites, or Force to take ownership with Server-Side Apply

Safe Rollouts at Scale

Change templates confidently without cluster-wide disruptions. Control blast radius with maxSkew — just like Kubernetes Deployment rolling updates.

All nodes update simultaneously

Waiting...

Controlled sliding window

Waiting...

🎯 Blast Radius Control

Limit concurrent updates with maxSkew. A bad template change affects only N nodes, not your entire fleet

🔄 Sliding Window

Not batch processing — as each node becomes Ready, the next update starts immediately. Parallel efficiency with controlled risk

📊 Real-time Progress

Track rollout status via kubectl get lynqforms or Prometheus metrics. Know exactly what's updating and when

Production Ready

Validated on Kubernetes v1.31 – v1.34

Production-tested across multiple versions • See compatibility details

Learn More

Explore comprehensive guides, API references, and real-world integration examples

📚

Core Concepts

⚙️

Operations

🔌

Integrations

Open source and actively maintained. Contributions, feedback, and questions are welcome

📦 GitHub Repository

k8s-lynq/lynq

Source code, releases, and project roadmap

🐛 Issue Tracker

Report Issues

Bug reports, feature requests, and discussions

📖 Documentation

Get Started →

Comprehensive guides and API reference