-
Notifications
You must be signed in to change notification settings - Fork 123
HorizontalPodAutoscaler Support #3447
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
Labels
community
enhancement
New feature or request
highlight
Relates to features that should be promoted despite not being an epic
Milestone
Comments
@mpstefan Thank! I'm using NGF2.0. For HPA, Do I have to apply hpa to control plane(ngf-nginx-gateway-fabric) or data plane(practice-gateway-nginx) or both of them? |
nowjean
pushed a commit
to nowjean/nginx-gateway-fabric
that referenced
this issue
Jun 14, 2025
| datasource | package | from | to | | ----------- | --------------------- | ------ | ------- | | github-tags | goreleaser/goreleaser | v2.9.0 | v2.10.2 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Add Nginx Gateway HPA(nginx#3447)
nowjean
pushed a commit
to nowjean/nginx-gateway-fabric
that referenced
this issue
Jun 14, 2025
Problem: There's a specific scenario where we can hit an out of bounds index while building route statuses. I don't know the exact scenario, but it involves a parentRef without a sectionName, on a Gateway with a single listener. Could possibly involve having multiple implementations being deployed as well. Solution: Adjust the logic to ensure we don't access indices that are out of bounds. Add Nginx Gateway HPA(nginx#3447)
nowjean
added a commit
to nowjean/nginx-gateway-fabric
that referenced
this issue
Jun 14, 2025
nowjean
pushed a commit
to nowjean/nginx-gateway-fabric
that referenced
this issue
Jun 14, 2025
Problem: There's a specific scenario where we can hit an out of bounds index while building route statuses. I don't know the exact scenario, but it involves a parentRef without a sectionName, on a Gateway with a single listener. Could possibly involve having multiple implementations being deployed as well. Solution: Adjust the logic to ensure we don't access indices that are out of bounds. ADD Nginx Gateway HPA(nginx#3447)
nowjean
pushed a commit
to nowjean/nginx-gateway-fabric
that referenced
this issue
Jun 14, 2025
| datasource | package | from | to | | ----------- | --------------------- | ------ | ------- | | github-tags | goreleaser/goreleaser | v2.9.0 | v2.10.2 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> ADD Nginx Gateway HPA(nginx#3447)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
community
enhancement
New feature or request
highlight
Relates to features that should be promoted despite not being an epic
Uh oh!
There was an error while loading. Please reload this page.
As a cluster operator using NGF
I want NGF to work with a HorizontalPodAutoscaler
So that I can automate the scaling of my data planes to save on resources and scale up when traffic increases.
NIC PR: nginx/kubernetes-ingress#3276
Acceptance
The text was updated successfully, but these errors were encountered: