Establish native illumos cluster baseline and repair API/TLS blockers #1
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/native-cluster-baseline-20261001"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The real illumos runtime failed to compile, both pod-list HTTP routes returned 500 before reconciliation could run, and
servestayed alive after API bind/TLS failure. Newly generated CA and server certificates also shared the same default subject, causing OpenSSL clients to reject the chain.Repair the native imports, separate namespaced and cluster-wide pod list/watch routes, propagate API failures, and give generated certificates distinct subjects plus an authority key identifier. Add a router regression and repeatable native build/API checks, exclude the mock NAT reload fixture on illumos, and correct the test fixture lints found by strict native Clippy. Existing TLS files are reused; this does not rotate an installed CA or certificate.
Validation on native OpenIndiana x86 with Rust 1.97.1, GCC 14, two build jobs and a dedicated Cargo target directory:
bash tools/check-native.sh: 189 workspace tests; binary build; formatting; Clippy across all targets with warnings denied; SMF manifest validation and method syntax.Update the stale README and document six dependency-linked cluster milestones: shared control plane/workers, component supervision, native images/zones, owned networking, API identity, and a packaged CI/runner pilot. Those milestones remain draft. No zone workload, host networking change, SMF activation, production deployment or multi-host cluster was performed. Native Anima CI configuration remains a pilot prerequisite.