Repository navigation
fix(helm,cli): CE-21 second slice — platform Aegra without DNS, atomic admission lock - #149
Merged
Merged
Conversation
…slice) Recon on tes2 showed the platform Aegra still resolved outside names through kube-dns. It now carries zelkor.io/dns-lockdown=on and zelkor.io/platform-release with dnsPolicy None and a dead nameserver: on K8s >= 1.36 the admission policy injects its hostAliases; on older clusters the chart reads the live host map with Helm lookup at upgrade (a first install keeps DNS, annotated inactive, until the next upgrade). Opt-out: security.dnsLockdown.aegra=false. The admission policy now selects by the dns-lockdown=on label (plus the platform release) instead of the workload type, so agents and the platform Aegra share one policy. qdrant joins the host map. zelkor verify --hosts also checks this platform's Aegra pods. S-90 adds the sandbox workers as a target: their egress is deny-all, DNS included. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On tes2 an upgrade that changed the policy selector created the platform
Aegra pod before the API server reloaded the policy. The template had
already set dnsPolicy None and dns-lockdown=on, so the pod came up with
no hostAliases and no port 53 and hung in its init containers.
On clusters with the admission API, charts now render pods with
zelkor.io/dns-lockdown=requested and normal DNS. The policy selects
requested and, in one mutation, sets dnsPolicy, dnsConfig, hostAliases
and the label "on". Port 53 is cut only for pods labelled on: the agent
chart's DNS rule moves to its own {release}-egress-dns policy keyed on
that label, like the platform ones. A pod the policy misses keeps
working DNS and zelkor verify --hosts warns to delete it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…is complete A map written by an older revision can lack a Service this revision adds (qdrant in 2.6.0). Locking Aegra on it would cut that name until the next upgrade, so on clusters without the admission API Aegra stays inactive until the map holds every platform name it calls. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CE-21 second slice, so 2.6.0 ships the whole DNS lockdown (the first slice, #148, covered
charts/zelkor-agentpods).Recon (tes2)
github.comresolved.sandboxMCPis on, and they call no names.runtime: appisn't built yet, so it's out of this slice.Changes
lookupat upgrade, but only when the map already holds every platform name Aegra calls. A first install, or a map from an older revision, keeps DNS (annotatedinactive) until the next upgrade.qdrantjoins the host map.security.dnsLockdown.aegra=false.dnsPolicy: None, so the pod hung with no host entries and no port 53. A fresh install could hit the same race.zelkor.io/dns-lockdown: requestedand keep normal DNS. The policy setsdnsPolicy,dnsConfig,hostAliasesand the labelonin one mutation.on. The agent chart's own DNS rule moves to{release}-egress-dns, keyed on that label.zelkor verify --hostsWARNs to delete it.zelkor verify --hostsalso checks this platform's Aegra pods and reportsrequestedpods.Proof
requested, Ready with DNS.verifyWARNed; after a pod delete it was locked.lookuppath):qdrant; its Job added it.verifycaughtrt-pydanticone name short untilzelkor deploy, then reported OK.finserve-alpharun through the public front door exited 0.Offline: 453 Helm and CLI tests pass.
🤖 Generated with Claude Code