You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The homogeneous Cilium device component is validated and staged, but production still references only the private-NIC component. That prevents the public default-route interfaces from receiving the eBPF programs required by the later masquerade and bandwidth-manager work.
Proposed direction
Activate the existing homogeneous-device component after the private-NIC component. Keep its OnDelete update strategy so the merge stages configuration without automatically restarting the fleet, and pin the resulting production render in CI.
Acceptance criteria
The production overlay references homogeneous-devices after private-nic-devices.
The rendered Cilium HelmRelease selects en+ eth+ and no longer resolves to the private-only device list.
The rendered rollout strategy is OnDelete, so node replacement remains operator-stepped.
WireGuard and the existing production encryption settings remain unchanged.
CI executes a fail-closed render contract for the activation and merge order.
The parent remains open for the post-merge node-by-node rollout, live verification, soak, and later removal of the temporary OnDelete override.
#2474 - refactor: name patch fragments by intent and codify patch naming rules [merged] #2507 - fix(apps): make actual-budget openid schema offline-resolvable [merged] #2524 - feat: enable the Hetzner floating-IP stable API endpoint on prod [merged] #2608 - feat(cilium): stage bandwidth manager with BBR [merged] #2620 - test(storage): restore userns smoke harness default-off [merged]
📝 Issue Planner
Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your .coderabbit.yaml:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Activity
coderabbitai commentedon Jul 22, 2026
🔗 Related PRs
#2474 - refactor: name patch fragments by intent and codify patch naming rules [merged]
#2507 - fix(apps): make actual-budget openid schema offline-resolvable [merged]
#2524 - feat: enable the Hetzner floating-IP stable API endpoint on prod [merged]
#2608 - feat(cilium): stage bandwidth manager with BBR [merged]
#2620 - test(storage): restore userns smoke harness default-off [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!