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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While this change correctly moves towards using the non-deprecated
IDfield, it could introduce a bug. If an existingVlancustom resource was created using only the deprecatedvlanIdfield,vlan.Spec.IDwould be0whilevlan.Spec.VlanIDholds the correct value. This would result in installing an FDB entry for VLAN 0, which is likely incorrect, as VLAN 0 is typically used for untagged traffic.To ensure backward compatibility during the transition period, I suggest adding a fallback to the deprecated field when the new
IDfield is not set. A more robust long-term solution would be to implement migration logic in thevlancontroller (or a conversion webhook) to populateIDfromVlanIDon resource reconciliation, makingIDthe single source of truth throughout the codebase.