HorizontalPodAutoscaling(HPA) on kubernetes nginx ingress Controller

[thejaswiniguduru]

I'm currently utilizing the Kubernetes Nginx Ingress Controller in Azure Kubernetes Service. In order to meet the security requirements raised by internal vulnerability scanning tool, I need to add CPU and MEMORY limits for the kind-role , for name: ingress-nginx-admission-create and name: ingress-nginx-admission-patch.

Kindly help me in knowing if HorizontalPodAutoscaling(HPA) can be enabled to the Nginx ingress controller version 1.9.3.

Please suggest on possible in-stability on adding CPU and MEMORY limits for the above mentioned area. since' InfoSecurity team detected possible vulnerability or information breach as shown in the below link.
https://avd.aquasec.com/misconfig/kubernetes/general/avd-ksv-0011/
https://avd.aquasec.com/misconfig/kubernetes/general/avd-ksv-0018/

The following Kubernetes Ingress Controller Manifest file is used in my project.
https://github.com/kubernetes/ingress-nginx/blob/main/deploy/static/provider/baremetal/deploy.yaml

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[longwuyuan]

/remove-kind bug Duplicate of #11005 /close

…

On Wed, 21 Feb, 2024, 8:59 pm Kubernetes Prow Robot, < ***@***.***> wrote: This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance. The triage/accepted label can be added by org members by writing /triage accepted in a comment. Instructions for interacting with me using PR comments are available here <https://git.k8s.io/community/contributors/guide/pull-requests.md>. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra <https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:> repository. — Reply to this email directly, view it on GitHub <#11006 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGZVWQHTPBEAGOK6ZBIPLDYUYHGTAVCNFSM6AAAAABDTIPRG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWHE2TEMRVGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to this:

/remove-kind bug

Duplicate of #11005

/close

On Wed, 21 Feb, 2024, 8:59 pm Kubernetes Prow Robot, <
@.***> wrote:

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will
accept it by applying the triage/accepted label and provide further
guidance.

The triage/accepted label can be added by org members by writing /triage
accepted in a comment.

Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:
repository.

—
Reply to this email directly, view it on GitHub
#11006 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABGZVWQHTPBEAGOK6ZBIPLDYUYHGTAVCNFSM6AAAAABDTIPRG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJWHE2TEMRVGA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.