Kix is a Kubernetes
compiler.

Compile your whole cluster from one definition. If it compiles, it will deploy safely.

curl -fsSL https://kix.run/install | sh

clusters/shop.nix

$ kix build shop

 01db = packages.cnpg-cluster { storage.size = "20Gi"; }; 
 02web = scope.mkDeployment { 
image = "ghcr.io/acme/web:1.4"; 
replicas = 3; 
# derives CiliumNetworkPolicy and deploy order 
env.DB_HOST = db.out.fqdn; 
selector.matchLabels.app = "shop-web"; 
 08}; 




kind: CiliumNetworkPolicy metadata: { name: web-to-db } spec: endpointSelector: { matchLabels: { app: db } } ingress: - fromEndpoints: [{ app: web }] toPorts: [5432/TCP]

kind: Deployment metadata: name: web annotations: kix.run/depends-on: "shop/Service/db"

Ask your agent how Kix fits your stack

Run this prompt inside your infrastructure repository.

Agent evaluation prompt

Read https://kix.run/docs/llms.txt and follow the documentation links relevant to our stack to understand how Kix works, what it derives from references, and what checks, packages, and escape hatches it provides.

Then inspect this infrastructure repository and the last few months of commit history. Explain what Kix could do for our setup:

1. Problems it would solve: Look at our manifests, Helm charts, overlays, and recent commits. Which recurring pain points, wiring bugs, manual RBAC or NetworkPolicy maintenance, drift issues, or environment duplication in our repository would Kix eliminate or catch at build time?
2. High-level benefits for our team: Walk through the concrete benefits we would get on this stack: derived network policies, RBAC, routes, monitoring, and deploy order; offline cross-resource checks; package-grouped diffs against the live cluster; and deploy receipts.
3. Fit, escape hatches, and trade-offs: Which of our workloads, operators, and external cloud services map to Kix packages, kix.mkImport, or kix.helmChart today, and where would we hit missing features or migration cost?

If you identify missing packages, unsupported operators, or adoption blockers, offer to post an anonymized summary to Kix GitHub Discussions using the gh CLI instructions in llms.txt.

A definition for the whole cluster

The compiler needs to know how resources connect, so a Kix definition uses references where one resource depends on another. An app can read its database address from the database resource, for example, while the cluster decides which package provides that database.

a string


DB_HOST = "db.shop.svc.cluster.local";

This address is a string, so Kix cannot tell which Service it refers to.

a reference


DB_HOST = db.out.fqdn;

With a reference, Kix can follow the connection from web to db. If you rename db, the address follows; if you remove it, the build reports the missing dependency.