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.

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

Automate Zero Downtime Scaling Test #1435

Closed
Tracked by #994
mpstefan opened this issue Jan 2, 2024 · 3 comments · Fixed by #2259
Closed
Tracked by #994

Automate Zero Downtime Scaling Test #1435

mpstefan opened this issue Jan 2, 2024 · 3 comments · Fixed by #2259
Assignees
Labels
refined Requirements are refined and the issue is ready to be implemented. size/large Estimated to be completed within two weeks tests Pull requests that update tests
Milestone

Comments

@mpstefan
Copy link
Collaborator

mpstefan commented Jan 2, 2024

As a maintainer of NGF
I want to automate the zero downtime scaling test
So that I do not need to run it manually in the future.

Acceptance

  • The zero downtime scaling test is automated to the point of being able to run the entire test from running a script.
  • The relevant results of the test are output as a result of the test.
@mpstefan mpstefan added this to the v1.3.0 milestone Jan 2, 2024
@mpstefan mpstefan added the tests Pull requests that update tests label Jan 2, 2024
Copy link
Contributor

github-actions bot commented Feb 6, 2024

This issue is stale because it has been open 14 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 Pull requests/issues with no activity label Feb 6, 2024
@sjberman sjberman removed the stale Pull requests/issues with no activity label Feb 6, 2024
@mpstefan mpstefan modified the milestones: v1.3.0, v2.0.0 Apr 23, 2024
@mpstefan mpstefan added refined Requirements are refined and the issue is ready to be implemented. size/large Estimated to be completed within two weeks labels Jun 17, 2024
@sjberman
Copy link
Contributor

sjberman commented Jul 15, 2024

@kate-osborn For the sake of automation, do you think we can adjust this test to use a single cluster? Right now it uses a 10 node cluster to ensure NGF is running multiple Pods on one node, and a 25 node cluster to ensure NGF runs 1 Pod per node.

Maybe we run with a 10 node cluster and run one test with 10 NGF Pods, and one test with 25 NGF pods. This way our pipeline doesn't need to manage two clusters, and we still test the same thing. Does that sound ok?

@kate-osborn
Copy link
Contributor

@sjberman yes, that sounds good

@sjberman sjberman self-assigned this Jul 15, 2024
@sjberman sjberman moved this from 🆕 New to 🏗 In Progress in NGINX Gateway Fabric Jul 15, 2024
@sjberman sjberman moved this from 🏗 In Progress to 👀 In Review in NGINX Gateway Fabric Jul 18, 2024
@github-project-automation github-project-automation bot moved this from 👀 In Review to ✅ Done in NGINX Gateway Fabric Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refined Requirements are refined and the issue is ready to be implemented. size/large Estimated to be completed within two weeks tests Pull requests that update tests
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants