Problem
$ kubectl get pods -n knative-serving
NAME READY STATUS RESTARTS AGE
activator-85ccbfb994-v6c8g 1/1 Running 2 (3m56s ago) 3h15m
autoscaler-cc8b7dbdb-9lg77 1/1 Running 2 (3m56s ago) 3h15m
controller-6f9fb85fbd-wd6lc 1/1 Running 2 (3m56s ago) 3h15m
domain-mapping-676b79f95b-8dqdz 1/1 Running 2 (3m56s ago) 3h15m
domainmapping-webhook-85bdfb7f6b-smx67 1/1 Running 3 (3m56s ago) 3h15m
net-istio-controller-5c767878f6-fsr6w 0/1 Pending 0 9m16s
net-istio-webhook-84f67c7f48-tqnq5 1/1 Running 1 (3m56s ago) 9m16s
webhook-664745d5cb-t26p5 1/1 Running 3 (3m56s ago) 3h15m
$ kubectl describe pod net-istio-controller-5c767878f6-fsr6w -n=knative-servin
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 8m31s default-scheduler 0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod.
Warning FailedScheduling 2m45s default-scheduler 0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod.
PS C:\minikube>
Solution
Start minikube with 16384 MB of memory and 4 CPUs
Latest posts by rajeshkumar (see all)
- Best DevOps is redefining the DevOps landscape - January 28, 2025
- Unlocking the Power of DevOps: How DevOps Consulting Drives Business Success - January 23, 2025
- DevOps Support: Ensuring Seamless Operations and Continuous Improvement - January 23, 2025