[1.6] ci: remove stage level pool field, isCustom, from e2e job templates #3899
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 removes stage-level pool configuration fields from multiple e2e job templates in Azure DevOps pipeline YAML files. The change eliminates the isCustom, type, and name fields from pool configurations because upstream validation changes now handle these fields automatically.
- Removes redundant pool configuration from stage templates
- Simplifies pipeline configuration by leveraging upstream validation
- Maintains consistent structure across all e2e job templates
Reviewed Changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.pipelines/singletenancy/dualstack-overlay/dualstackoverlay-e2e.stages.yaml | Removed pool configuration block with isCustom, type, and name fields |
.pipelines/singletenancy/cilium-overlay/cilium-overlay-e2e.stages.yaml | Removed pool configuration block with isCustom, type, and name fields |
.pipelines/singletenancy/cilium-overlay-withhubble/cilium-overlay-e2e.stages.yaml | Removed pool configuration block with isCustom, type, and name fields |
.pipelines/singletenancy/cilium-nodesubnet/cilium-nodesubnet-e2e.stages.yaml | Removed pool configuration block with isCustom, type, and name fields |
.pipelines/singletenancy/cilium-dualstack-overlay/cilium-dualstackoverlay-e2e.stages.yaml | Removed pool configuration block with isCustom, type, and name fields |
.pipelines/singletenancy/azure-cni-overlay/azure-cni-overlay-e2e.stages.yaml | Removed pool configuration block with isCustom, type, and name fields |
.pipelines/singletenancy/azure-cni-overlay-stateless/azure-cni-overlay-stateless-e2e.stages.yaml | Removed pool configuration block with isCustom, type, and name fields |
.pipelines/singletenancy/aks/e2e.stages.yaml | Removed pool configuration block with isCustom, type, and name fields |
.pipelines/singletenancy/aks-swift/e2e.stages.yaml | Removed pool configuration block with isCustom, type, and name fields |
| /azp run Azure Container Networking PR |
| Azure Pipelines successfully started running 1 pipeline(s). |
rbtr approved these changes Aug 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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:
Upstream validation changes now capture for these fields
Issue Fixed:
Requirements:
Notes: