Deploy nginx-ingress using Fargate on EKS with version 1.25

[lmbruder]

What happened: The following error after trying to use nginx-ingress with EKS and Fargate: Pod not supported on Fargate: invalid SecurityContext fields: AllowPrivilegeEscalation

What you expected to happen: I expected the nginx-ingress pod to start normally after installing the helm chart as follows: helm install nginx-ingress nginx-stable/nginx-ingress --namespace ingress-nginx -f nginx-values.yml

with nginx-values being:

controller:
  extraArgs:
    http-port: 8080
    https-port: 8081

  containerPort:
    http: 8080
    https: 8081

  image:
    allowPrivilegeEscalation: false

  service:
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-type: "nlb-ip"

as described in this issue: https://github.com/kubernetes/ingress-nginx/issues/4888#issuecomment-964535071

It seems like the value allowPrivilegeEscalation: false is not overwritten as expected or am I missing something else?

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.): Cannot exec into the pod because it is not running, but the image is the follwing: nginx/nginx-ingress:3.0.2

Kubernetes version (use kubectl version): Client Version: v1.26.0 Kustomize Version: v4.5.7 Server Version: v1.25.6-eks-48e63af

Environment:

• Cloud provider or hardware configuration: AWS

• How was the ingress-nginx-controller installed:

  NAME                            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                                   APP VERSION
  nginx-ingress                   ingress-nginx   1               2023-03-07 11:55:47.4917287 +0100 CET   deployed        nginx-ingress-0.16.2                    3.0.2

• Current State of the controller:

  
  Name:         alb
  Labels:       app.kubernetes.io/instance=aws-load-balancer-controller
            app.kubernetes.io/managed-by=Helm
            app.kubernetes.io/name=aws-load-balancer-controller
            app.kubernetes.io/version=v2.4.6
            helm.sh/chart=aws-load-balancer-controller-1.4.7
  Annotations:  meta.helm.sh/release-name: aws-load-balancer-controller
            meta.helm.sh/release-namespace: kube-system
  Controller:   ingress.k8s.aws/alb
  Events:       <none>

Name: nginx Labels: app.kubernetes.io/managed-by=Helm Annotations: meta.helm.sh/release-name: nginx-ingress meta.helm.sh/release-namespace: ingress-nginx Controller: nginx.org/ingress-controller Events:

**How to reproduce this issue**:
- Use a version 1.25 EKS cluster
- install with helm as described above

[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](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.

[longwuyuan]

This helm install nginx-ingress nginx-stable/nginx-ingress is not a release from this project. Please check docs /remove-kind bug /close

[k8s-ci-robot]

@longwuyuan: Closing this issue.

In response to [this](https://github.com/kubernetes/ingress-nginx/issues/9704#issuecomment-1458009255): >This **helm install nginx-ingress nginx-stable/nginx-ingress** is not a release from this project. Please check docs >/remove-kind bug >/close 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.