Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automate CNI plugin upgrade testing #694

Closed
1 of 2 tasks
jaypipes opened this issue Oct 29, 2019 · 6 comments · Fixed by #1863
Closed
1 of 2 tasks

Automate CNI plugin upgrade testing #694

jaypipes opened this issue Oct 29, 2019 · 6 comments · Fixed by #1863
Assignees
@cgchinmay
Labels
priority/P2 Low priority, nice to have. testing

Comments

@jaypipes
Copy link
Contributor

jaypipes commented Oct 29, 2019 •
edited by mogren
Loading

Before releases, we manually perform a test of the upgrade process for the CNI plugin:

  1. create 3 c3.xlarge node cluster
  2. scale pod replica from 0 to 130
  3. verify kubectl get deployment
  4. upgrade cni to new version
  5. verify kubectl get deployment
  6. scale replica from 130 to 0
  7. verify kubectl get deployment
  8. scale replica from 0 to 130 again and verify

We should automate this and gate all PRs on a successful upgrade test

  • Convert above steps into a Bash script
  • Add job to CircleCI pipeline, gating for all PRs
@jaypipes jaypipes added priority/P0 Highest priority. Someone needs to actively work on this. testing labels Oct 29, 2019
@mogren mogren self-assigned this Nov 4, 2019
@mogren
Copy link
Contributor

mogren commented Feb 21, 2020

The current test script doesn't scale up and down.

@mogren mogren added priority/P2 Low priority, nice to have. and removed priority/P0 Highest priority. Someone needs to actively work on this. labels Sep 4, 2020
@jayanthvn jayanthvn assigned abhipth and unassigned mogren Apr 9, 2021
@jayanthvn jayanthvn assigned Shreya027 and unassigned abhipth Oct 19, 2021
@jayanthvn
Copy link
Contributor

  1. Scale up to 130 pods (Ref performance script)
  2. Run traffic test from the new integration scripts.
  3. Upon success, scale down to 0
  4. Upgrade to latest CNI
  5. Repeat 1-3 steps.

@Shreya027 Shreya027 mentioned this issue Dec 16, 2021
Closed
@jayanthvn jayanthvn assigned cgchinmay and unassigned Shreya027 Feb 25, 2022
@jayanthvn
Copy link
Contributor

@cgchinmay - Can we include this issue as part of this PR - #1863

@jayanthvn jayanthvn mentioned this issue Mar 8, 2022
Merged
@github-actions
Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

@github-actions github-actions bot added the stale Issue or PR is stale label Apr 27, 2022
@jayanthvn
Copy link
Contributor

/not stale

@github-actions github-actions bot removed the stale Issue or PR is stale label Apr 28, 2022
@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cgchinmay cgchinmay

Labels
priority/P2 Low priority, nice to have. testing
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

cni manifest upgrade downgrade test cgchinmay/amazon-vpc-cni-k8s
6 participants
@mogren @jaypipes @jayanthvn @cgchinmay @Shreya027 @abhipth