-
Notifications
You must be signed in to change notification settings - Fork 246
ci: [1/?] Automated version update pipeline #3667
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
base: master
Are you sure you want to change the base?
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 introduces automated version management for AKS cluster creation pipelines by leveraging variable groups and adds support for a Long Term Support (LTS) flag.
- Added
LTS_ARGS
inhack/aks/Makefile
to conditionally apply LTS options toaz aks create
commands - Extended the cluster creation template to accept an
LTS
parameter - Configured pipeline jobs to pass the
LTS
flag based on Kubernetes version
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
File | Description |
---|---|
hack/aks/Makefile | Define LTS_ARGS and inject into cluster creation targets |
.pipelines/templates/create-cluster-steps.yaml | Add LTS parameter usage in the cluster creation steps template |
.pipelines/cni/ado-automation/var-pipeline.yaml | Set LTS flag in pipeline job parameters for specific versions |
Comments suppressed due to low confidence (1)
.pipelines/templates/create-cluster-steps.yaml:1
- The template references a parameter 'LTS' in the steps but it isn't defined under
parameters:
. Add a definition likeLTS: false
(or an appropriate default) to ensure the flag is recognized.
parameters:
d6dfe62
to
b4a383f
Compare
b4a383f
to
3bcbabf
Compare
/azp run Azure Container Networking PR |
Azure Pipelines successfully started running 1 pipeline(s). |
Reason for Change:
Maintenace for multiple release train versions are slipping. This PR is the first of multiple to leverage variable groups to allow E2E pipelines to use latest managed version where applicable.
Issue Fixed:
Requirements:
Notes: