2 commits

Author	SHA1	Message	Date
Claude	d8425ad85d	Add service networking, bhyve brand, ipadm IP config, and zone state reporting ... Service networking: - ClusterIP IPAM allocation on service create/delete via reusable Ipam with_prefix() - ServiceController watches Pod/Service events + periodic reconcile to track endpoints - NatManager generates ipnat rdr rules for ClusterIP -> pod IP forwarding - Embedded DNS server resolves {svc}.{ns}.svc.cluster.local to ClusterIP - New CLI flags: --service-cidr (default 10.96.0.0/12), --cluster-dns (default 0.0.0.0:10053) Quick wins: - ipadm IP assignment: configure_zone_ip() runs ipadm/route inside zone via zlogin after boot - Node heartbeat zone state reporting: reddwarf.io/zone-count and zone-summary annotations - bhyve brand support: ZoneBrand::Bhyve, install args, zonecfg device generation, controller integration 189 tests passing, clippy clean. https://claude.ai/code/session_016QLFjAyYGzMPbBjEGMe75j	2026-03-19 20:28:40 +00:00
Till Wegmueller	57186ebe68	Add pod networking: IPAM, per-pod VNICs, and zone IP configuration ... Each pod now gets a unique VNIC name and IP address from a configurable CIDR pool, with IPs released on pod deletion. This replaces the hardcoded single VNIC/IP that prevented multiple pods from running. - Add redb-backed IPAM module with allocate/release/idempotent semantics - Add prefix_len to EtherstubConfig and DirectNicConfig - Generate allowed-address and defrouter in zonecfg net blocks - Wire vnic_name_for_pod() into controller for unique VNIC names - Add --pod-cidr and --etherstub-name CLI flags to agent subcommand - Add StorageError and IpamPoolExhausted error variants with diagnostics Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-09 00:17:45 +01:00