Closed lmbruder closed 1 year ago
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.
This helm install nginx-ingress nginx-stable/nginx-ingress is not a release from this project. Please check docs /remove-kind bug /close
@longwuyuan: Closing this issue.
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:
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-48e63afEnvironment:
Cloud provider or hardware configuration: AWS
How was the ingress-nginx-controller installed:
Current State of the controller:
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: