-
Notifications
You must be signed in to change notification settings - Fork 260
[backport] v1.6 ci: [CNS] Overlay Expansion Subnet Update Job Bug Fix #4103 #4114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
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.
Pull Request Overview
This PR backports a bug fix for the CNS Overlay Expansion Subnet Update Job to v1.6. The fix enables CNS to accept network container subnet expansions by validating whether a new subnet is a superset of the existing subnet, rather than failing when any subnet change is detected.
Key Changes:
- Added subnet superset validation logic to allow overlay subnet expansion scenarios
- Enhanced test coverage with multiple test cases for both valid and invalid subnet changes
- Refactored tests to use table-driven test patterns
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| cns/restserver/internalapi.go | Added conditional logic to validate if new subnet is a superset of existing subnet before rejecting NC updates |
| cns/restserver/internalapi_test.go | Converted single test case to table-driven tests and added new test function for valid subnet expansion scenarios |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Reason for Change:
Backporting subnet overlay expansion to v1.6
Issue Fixed:
Requirements:
Notes: