Error:
$ kubectl -n istio-system get deploy
NAME READY UP-TO-DATE AVAILABLE AGE
istio-ingressgateway 2/3 3 2 15d
istiod 3/3 3 3 15d
$ kubectl -n istio-system get pods
NAME READY STATUS RESTARTS AGE
istio-ingressgateway-7f87959cf9-j4lf9 0/1 Pending 0 15d
istio-ingressgateway-7f87959cf9-smxvk 1/1 Running 7 (14m ago) 15d
istio-ingressgateway-7f87959cf9-vggz8 1/1 Running 6 (14m ago) 15d
istiod-79597b775c-ffkn2 1/1 Running 7 (14m ago) 15d
istiod-79597b775c-wktks 1/1 Running 0 15d
istiod-79597b775c-wrs9w 1/1 Running 8 (14m ago) 15d
$ kubectl describe pod istio-ingressgateway-7f87959cf9-j4lf9 -n=istio-system
Warning FailedScheduling 28m (x43 over 3h31m) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod.
Warning FailedScheduling 15m (x2 over 20m) default-scheduler 0/1 nodes are available: 1 Insufficient memory. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod.
Warning FailedScheduling 4m49s (x2 over 9m50s) default-scheduler 0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod.
Latest posts by rajeshkumar (see all)
- Gitlab Error: - March 8, 2023
- Kubernestes EKS Error: Readiness probe failed /app/grpc-health-probe -addr=:50051 - February 28, 2023
- SSL Error: no alternative certificate subject name matches target - February 24, 2023