Closed limylily closed 2 years ago
@meng-yu-github: 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.
/remove-kind bug
Describe in complete detail about what problem needs to be solved
I want the status of the following two pods to be running
NAME READY STATUS RESTARTS AGE
pod/ingress-nginx-admission-create--1-pcgvw 0/1 Completed 0 24h
pod/ingress-nginx-admission-patch--1-zhh7d 0/1 Completed 1 24h
They are not expected to be running. /close
@longwuyuan: Closing this issue.
I do have the same issue. I was following the QuickStart and run the kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/kind/deploy.yaml
. So seems the ingress-nginx-controller
just got stuck and never goes from the Pending state...
kubectl -n ingress-nginx describe pods ingress-nginx-controller-77f58bf6cd-tl6xt
Warning FailedScheduling 94s default-scheduler 0/1 nodes are available: 1 node(s) didn't match Pod's node affinity/selector. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
Same here
I want the status of the following two pods to be running
NAME READY STATUS RESTARTS AGE pod/ingress-nginx-admission-create--1-pcgvw 0/1 Completed 0 24h pod/ingress-nginx-admission-patch--1-zhh7d 0/1 Completed 1 24h
have u solved this problem year ago? i really need the solution
Hi! I used YAML for deployment of ingress-nginx, but pod did not start successfully.
Information about deployed resources:
Information about pod/ingress-nginx-admission-create--1-pcgvw
Information about pod/ingress-nginx-admission-patch--1-zhh7d
Kubernetes version
Current State of the controller
What you expected to happen: I want it to work