ci: cns patch testing in release pipeline #3914
Open
Conversation
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
There was a problem hiding this comment.
Pull Request Overview
This PR extends the CNS patch testing capability to CNIv2 scenarios in the release pipeline. It allows for testing CNS version upgrades by configuring specific pipeline variables and adds conditional logic to support both regular and upgrade scenarios.
Key changes:
- Added upgrade scenario support to CNIv2 templates with conditional logic for version handling
- Enhanced log artifact naming to differentiate between regular and upgrade test runs
- Extended pipeline configuration to include CNIv2 upgrade test stages alongside existing Cilium upgrade tests
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 12 comments.
| File | Description |
|---|---|
| .pipelines/npm/npm-cni-integration-test.yaml | Added configurable log type parameter for artifact naming |
| .pipelines/cni/singletenancy/cniv2-template.yaml | Added upgrade scenario support with conditional stage creation and CNS version handling |
| .pipelines/cni/pipeline.yaml | Added CNIv2 upgrade test stages and updated documentation comment |
| .pipelines/cni/cilium/cilium-overlay-load-test-template.yaml | Fixed job dependency to include CNS deployment |
jpayne3506
approved these changes
Aug 12, 2025
vipul-21
approved these changes
Aug 14, 2025
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reason for Change:
Allows for bumping the cns version in the release pipeline byo clusters to test upgrades to the next version. CNS patch test is already in place for cilium scenarios, this PR extends it to the CNIv2 scenarios.
Requires setting upgradeScenario: true in pipeline trigger and updating the following variables:
TEST_CNS_VERSION: set to current cns patchCNS_IMAGE_REPO: set the repo for current cns imageUPGRADE_CNS_VERSION: set to upgrade cns patchUPGRADE_CNS_IMAGE_REPO: set the repo for upgrade imageContinuation of #3678
Issue Fixed:
Requirements:
Notes: