feat(imp): VTEP guardrail canary on unraid-lab - #52
Merged
Conversation
- pin imp + imp-crds apps to imp@906bf04c7fc5 (adds ClusterImpNodeProfile spec.vtepIP; agent resolves it via direct client pre-manager) - bump agent/runtime digest to vtep-direct build e5967c476a2f imp-crds was pinned to v0.6.1 and kept pruning spec.vtepIP from node profiles — root cause of the silent VTEP config loss.
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
1 participant
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.
Pins imp + imp-crds ArgoCD apps to imp@906bf04c7fc5 and bumps agent/runtime to digest e5967c476a2f.
Why imp-crds mattered
imp-crds was pinned to v0.6.1; its selfHeal kept reverting clusterimpnodeprofiles CRD schema, silently pruning spec.vtepIP from every profile. This was the root cause of VTEP config loss during earlier canary attempts.
Canary content (imp PR #53)