Skip to content

feat(imp): deploy VTEP guardrail to unraid-lab - #51

Merged
syscod3 merged 3 commits into
mainfrom
feat/imp-vtep-guardrail
Aug 25, 2026
Merged

syscod3 merged 3 commits into
mainfrom
feat/imp-vtep-guardrail

Conversation

@syscod3

@syscod3 syscod3 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Deploys VTEP guardrail to unraid-lab cluster to fix cross-node duplicate InternalIP regression.

Changes

  • Updated agent and runtime images to VTEP-guardrail version (sha256:e000f6219b7fd3d45dbe055e1c4489d5c4e850b94e602d8d2df179ee758957df)
  • Includes ClusterImpNodeProfile.spec.vtepIP field for stable VTEP identity
  • Made VTEP resolution non-fatal to prevent agent startup failures

Issue Fixed

Fixes the cross-node duplicate InternalIP regression where nodes advertised duplicate gateway addresses (10.251.0.1) because the runtime created guest bridges with gateway matching kubelet-selected status.hostIP.

Verification

  • All tests pass in imp repo
  • Lint passes in imp repo
  • E2E tests pass with new node labeling fix
  • VTEP guardrail tested locally

- Updated agent and runtime images to VTEP-guardrail version
- Includes ClusterImpNodeProfile.spec.vtepIP field for stable VTEP identity
- Made VTEP resolution non-fatal to prevent agent startup failures

This fixes the cross-node duplicate InternalIP regression where nodes
advertised duplicate gateway addresses.
@syscod3
syscod3 merged commit 6b146c0 into main Aug 25, 2026
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