-
Notifications
You must be signed in to change notification settings - Fork 109
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 Scale Test #1368
Labels
refined
Requirements are refined and the issue is ready to be implemented.
size/medium
Estimated to be completed within a week
tests
Pull requests that update tests
Milestone
Comments
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. |
pleshakov
added a commit
to pleshakov/nginx-gateway-fabric
that referenced
this issue
May 2, 2024
Problem: Non-functional scale test needs to be run manually. Solution: - Automate scale test. - Use in-cluster Prometheus to collect CPU, memory and NGF metrics. - Use Kubernetes API server to get NGF logs. For development and troubleshooting, it is possible to run scale test locally in Kind cluster. However, it is necessary to bring down the number of HTTPRoutes to 50 or less (roughly). Testing: - Ran this test locally with 64 listeners, 50 routes and 50 upstreams. - Ran this test on GKE with the default configuration. Out of scope: ensuring this test runs successfully via GitHub pipeline. Closes nginx#1368 Largely based on work by Ciara in nginx#1804 Co-authored-by: Ciara Stacke <[email protected]>
pleshakov
added a commit
to pleshakov/nginx-gateway-fabric
that referenced
this issue
May 2, 2024
Problem: Non-functional scale test needs to be run manually. Solution: - Automate scale test. - Use in-cluster Prometheus to collect CPU, memory and NGF metrics. - Use Kubernetes API server to get NGF logs. For development and troubleshooting, it is possible to run scale test locally in Kind cluster. However, it is necessary to bring down the number of HTTPRoutes to 50 or less (roughly). Testing: - Ran this test locally with 64 listeners, 50 routes and 50 upstreams. - Ran this test on GKE with the default configuration. Out of scope: ensuring this test runs successfully via GitHub pipeline. Closes nginx#1368 Largely based on work by Ciara in nginx#1804 Co-authored-by: Ciara Stacke <[email protected]>
pleshakov
added a commit
to pleshakov/nginx-gateway-fabric
that referenced
this issue
May 2, 2024
Problem: Non-functional scale test needs to be run manually. Solution: - Automate scale test. - Use in-cluster Prometheus to collect CPU, memory and NGF metrics. - Use Kubernetes API server to get NGF logs. For development and troubleshooting, it is possible to run scale test locally in Kind cluster. However, it is necessary to bring down the number of HTTPRoutes to 50 or less (roughly). Testing: - Ran this test locally with 64 listeners, 50 routes and 50 upstreams with NGINX OSS. - Ran this test on GKE with the default configuration with NGINX OSS. Out of scope: ensuring this test runs successfully via GitHub pipeline. Closes nginx#1368 Largely based on work by Ciara in nginx#1804 Co-authored-by: Ciara Stacke <[email protected]>
pleshakov
added a commit
to pleshakov/nginx-gateway-fabric
that referenced
this issue
May 16, 2024
Problem: Non-functional scale test needs to be run manually. Solution: - Automate scale test. - Use in-cluster Prometheus to collect CPU, memory and NGF metrics. - Use Kubernetes API server to get NGF logs. For development and troubleshooting, it is possible to run scale test locally in Kind cluster. However, it is necessary to bring down the number of HTTPRoutes to 50 or less (roughly). Testing: - Ran this test locally with 64 listeners, 50 routes and 50 upstreams with NGINX OSS. - Ran this test on GKE with the default configuration with NGINX OSS. Out of scope: ensuring this test runs successfully via GitHub pipeline. Closes nginx#1368 Largely based on work by Ciara in nginx#1804 Co-authored-by: Ciara Stacke <[email protected]>
pleshakov
added a commit
to pleshakov/nginx-gateway-fabric
that referenced
this issue
May 17, 2024
Problem: Non-functional scale test needs to be run manually. Solution: - Automate scale test. - Use in-cluster Prometheus to collect CPU, memory and NGF metrics. - Use Kubernetes API server to get NGF logs. For development and troubleshooting, it is possible to run scale test locally in Kind cluster. However, it is necessary to bring down the number of HTTPRoutes to 50 or less (roughly). Testing: - Ran this test locally with 64 listeners, 50 routes and 50 upstreams with NGINX OSS. - Ran this test on GKE with the default configuration with NGINX OSS. Out of scope: ensuring this test runs successfully via GitHub pipeline. Closes nginx#1368 Largely based on work by Ciara in nginx#1804 Co-authored-by: Ciara Stacke <[email protected]>
pleshakov
added a commit
that referenced
this issue
May 17, 2024
Problem: Non-functional scale test needs to be run manually. Solution: - Automate scale test. - Use in-cluster Prometheus to collect CPU, memory and NGF metrics. - Use Kubernetes API server to get NGF logs. For development and troubleshooting, it is possible to run scale test locally in Kind cluster. However, it is necessary to bring down the number of HTTPRoutes to 50 or less (roughly). Testing: - Ran this test locally with 64 listeners, 50 routes and 50 upstreams with NGINX OSS. - Ran this test locally with 64 listeners, 10 routes and 10 upstreams with NGINX Plus. - Ran this test on GKE with the default configuration with NGINX OSS. Out of scope: ensuring this test runs successfully via GitHub pipeline. Closes #1368 Largely based on work by Ciara in #1804 Co-authored-by: Ciara Stacke <[email protected]>
miledxz
added a commit
to miledxz/nginx-gateway-fabric
that referenced
this issue
Jan 14, 2025
Problem: Non-functional scale test needs to be run manually. Solution: - Automate scale test. - Use in-cluster Prometheus to collect CPU, memory and NGF metrics. - Use Kubernetes API server to get NGF logs. For development and troubleshooting, it is possible to run scale test locally in Kind cluster. However, it is necessary to bring down the number of HTTPRoutes to 50 or less (roughly). Testing: - Ran this test locally with 64 listeners, 50 routes and 50 upstreams with NGINX OSS. - Ran this test locally with 64 listeners, 10 routes and 10 upstreams with NGINX Plus. - Ran this test on GKE with the default configuration with NGINX OSS. Out of scope: ensuring this test runs successfully via GitHub pipeline. Closes nginx#1368 Largely based on work by Ciara in nginx#1804 Co-authored-by: Ciara Stacke <[email protected]>
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/medium
Estimated to be completed within a week
tests
Pull requests that update tests
As a maintainer of NGF
I want to automate the scale test
So that I do not need to run it manually in the future.
Acceptance
The text was updated successfully, but these errors were encountered: