Skip to content Your Database.
Infrastructure as Data
Your Database.
Your Infrastructure.
Lynq turns database records into Kubernetes resources. Automatically.
Database
Kubernetes
Scroll to explore
↓
15resource types
3lifecycle policies
MySQL & PostgreSQLbuilt-in datasources
Kubernetes 1.28+cluster requirement
MITopen source license
How It Works
From Data to Resources in Seconds
Click each step to explore the full lifecycle — from database row to running Kubernetes resources
Database
MySQL / PostgreSQL
sync
LynqHub
Data Source
data
LynqForm
Template
apply
Kubernetes
Resources
Step 1
Connect Your Database
LynqHub polls your MySQL or PostgreSQL table at the configured syncInterval (default: 1 minute). Any row where the activate column is truthy gets a corresponding LynqNode CR. Existing infrastructure keeps running if the database goes temporarily offline.
lynqhub.yamlYAML
apiVersion: operator.lynq.sh/v1
kind: LynqHub
metadata:
name: my-hub
spec:
source:
type: mysql
syncInterval: 1m
mysql:
host: mysql.default.svc
port: 3306
username: node_reader
passwordRef:
name: mysql-credentials
key: password
database: nodes
table: node_configsThe Problem
Your Database Knows. Your Cluster Doesn't.
The Old Way
- Manual kubectl for each customer
- Git commits for every change
- Constant drift between DB and cluster
vs
With Lynq
- One LynqForm template per resource type
- INSERT a row → resources appear within 60s
- DELETE a row → resources are cleaned up
Policies
Precise Lifecycle Control
Per-resource policies for creation, deletion, conflict resolution, and rollout pacing
conflictPolicy
Conflict Detection
Halts if another controller owns the resource. Choose Stuck to surface conflicts or Force to take ownership.
conflictPolicy: StuckmaxSkew
Gradual Rollout
Limit how many nodes update simultaneously when a LynqForm template changes.
maxSkew: 2deletionPolicy
Retain on Delete
Keep specific resources (PVCs, Secrets) when a row is deactivated. Resources get orphan markers for audit.
deletionPolicy: RetainDashboard
Observe the Full Hub → Form → Node Graph
A web UI that shows live resource health, reconciliation events, and topology relationships — no kubectl required
localhost:8080/topology
Topology ViewHub → Form → Node hierarchy with live status
Resource HealthReady, pending, failed counts per node
Event StreamReconciliation events and error details per node
Quick Search⌘K to find any hub, form, or node instantly
Blog
Latest from the Blog
Insights on Infrastructure as Data, Kubernetes operations, and Lynq updates
Is It Okay to Delegate Business Logic to Infrastructure?
Thoughts on delegating business logic to the infrastructure layer, through the lens of Uber embedding Rate Limiting into their service mesh
Read article →In the Age of AI Agents, How Should Infrastructure Change?
The era of AI Agents autonomously managing infrastructure is coming. But do we have an answer to the question, 'When AI decides, who executes?'
Read article →Introducing Lynq Dashboard
Lynq Dashboard is now available. A web UI to visualize Hub-Form-Node relationships and quickly identify problematic resources.
Read article →LynqHubLynqFormLynqNodeMySQLDeploymentServiceIngressConfigMapSecretStatefulSetCronJobPVCNamespacePostgreSQLStart Automating Infrastructure from Your Database
Requires Kubernetes and cert-manager. The quickstart provisions a full local environment — MySQL, Lynq, and sample resources — using automated setup scripts.