Production is lattice-install on Ubuntu. Kubernetes is not a product SKU and not a hosted Lattice cluster. Prefer the installer unless you already run k8s as a platform. Community is one Ubuntu node. Starter HA is three-node Patroni on one L2 (the trio, not your clients), not these manifests. HA.
Postgres stays external. Do not run a single-pod database as the lease store. Relays, VIP, and DHCP snooping still sit on the network fabric.
If you still run the example manifests:
- Point Deployments at your registry tags. No
latest. - Set
LATTICE_PG_DSN(sslmode=require) andLATTICE_TRUSTED_RELAYS. - Front the API with an Ingress on HTTPS. Front dhcpd with an anycast VIP or per-node listeners (VIP).
API /readyz is the load-balancer health check. dhcpd HTTP /readyz is Postgres ping plus a subnet-count query.
Entitlement
Admins can upload lattice.entitlement.json in the console; Lattice stores it in Postgres so every process sees it. Or mount the file at /etc/lattice/entitlement.json for api, dhcpd, and worker. Missing or invalid file is community (1,000 IPs). License.
What this is not
- Not a BGP speaker. Document FRR/BIRD beside the cluster.
- Not a substitute for DHCP snooping and trusted relays on the switching fabric.