Lynq turns database records into Kubernetes resources. Automatically.

Click each step to see how Lynq transforms database records into Kubernetes resources
LynqHub connects to your existing MySQL database and periodically syncs active records that should have Kubernetes resources.
apiVersion: operator.lynq.sh/v1
kind: LynqHub
metadata:
name: my-hub
spec:
source:
type: mysql
syncInterval: 30s
mysql:
host: mysql.default.svc
port: 3306
username: node_reader
passwordRef:
name: mysql-credentials
key: password
database: nodes
table: node_configsBuilt-in policies prevent disasters before they happen
Stops reconciliation if another controller already owns the resource. No silent overwrites.
conflictPolicy: StuckLimit concurrent updates. Change 500 resources safely, a few at a time.
maxSkew: 2Keep critical resources (like PVCs) even when the source record is deleted.
deletionPolicy: RetainMonitor Hub-Form-Node relationships and quickly identify issues
Insights on Infrastructure as Data, Kubernetes operations, and Lynq updates
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 →Lynq Dashboard is now available. A web UI to visualize Hub-Form-Node relationships and quickly identify problematic resources.
Read article →Real-world problems that occur when managing Kubernetes resources at scale, and how Lynq's policy system prevents them.
Read article →LynqHubLynqFormLynqNodeMySQLDeploymentServiceIngressConfigMapSecretStatefulSetCronJobPVCNamespacePostgreSQLGet started with Lynq in minutes. No complex setup required.