Skip to content

feat: adopt externally-provided server key (survive namespace rebuild)#9

Draft
mxhob1 wants to merge 1 commit into
noden/mainfrom
feat/server-key-adopt-external
Draft

feat: adopt externally-provided server key (survive namespace rebuild)#9
mxhob1 wants to merge 1 commit into
noden/mainfrom
feat/server-key-adopt-external

Conversation

@mxhob1

@mxhob1 mxhob1 commented Jun 7, 2026

Copy link
Copy Markdown
Member

Extends the peer key-provenance pattern (#2 / 347f8a7) to the SERVER key — the one place it was missed. On a namespace rebuild the operator currently mints a NEW server key (wireguard_controller.go:852 unconditional GeneratePrivateKey), so every peer breaks (they hold the old server pubkey). Fix: when a Wireguard CR is annotated vpn.wireguard-operator.io/server-key-source: external, the reconciler waits (requeue) for external-secrets to create the wireguard Secret and adopts it, instead of minting; and it derives the pubkey if ESO seeded only the privateKey. Build+vet clean. Tests run in CI (envtest needs KUBEBUILDER_ASSETS). DRAFT — branch-only, rolls to prod in a maintenance window (image pin stays ba5f12d). 🤖 Generated with Claude Code

… wireguard Secret instead of minting when annotated vpn.wireguard-operator.io/server-key-source=external; derive pubkey if only privateKey seeded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant