-
Notifications
You must be signed in to change notification settings - Fork 242
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
ci:[CNI] Remove load balancer tests and add rollout status for konnectivity-agent in ACN PR pipeline #2072
Conversation
a958fd2
to
111ee09
Compare
111ee09
to
2eddcd5
Compare
@@ -65,17 +65,6 @@ jobs: | |||
os: ${{ parameters.os }} | |||
processes: 8 | |||
attempts: 3 | |||
- ${{ if eq(parameters.loadBalancer, true) }}: |
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.
Let's make a note of everything we removing from PR pipeline should be added to cni release pipeline.
@@ -25,6 +25,7 @@ steps: | |||
# Taint Linux nodes so that windows tests do not run on them | |||
if ${{ lower(eq(parameters.os, 'windows')) }} | |||
then | |||
kubectl rollout status -n kube-system deployment/konnectivity-agent --timeout=3m |
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.
Is this just for windows, or we need to wait for the deployment in linux as well ?
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.
Just for windows due to the linux node being tainted, stopping scheduling for system assets while windows tests are running.
…tivity-agent in ACN PR pipeline (#2072) * Remove Loadbalancer Tests * Add status check for konnectivity agent
#2487) ci:[CNI] Remove load balancer tests and add rollout status for konnectivity-agent in ACN PR pipeline (#2072) * Remove Loadbalancer Tests * Add status check for konnectivity agent Co-authored-by: John Payne <[email protected]>
Reason for Change:
Windows e2e test require a taint on linux nodes to ensure that the tests run on the windows nodepool. This has led to konnectivity-agent pods restarting in the middle of tests without enough time to restart. Resulting in e2e tests unable to start or recover in-between steps.
Removing load balancer tests as they are not required for CNI e2e testing.
Issue Fixed:
Requirements:
Notes: