Istio-pilot component pod is in pending state

#1

I have minikube installed on Linux vm and I preparing Istio installation with mTLS. istio-pilot pod is in pending state.
Pod description below:
root@asdf:/istio-1.0.5# kubectl describe deployment istio-pilot -n istio-system
Name: istio-pilot
Namespace: istio-system
CreationTimestamp: Tue, 15 Jan 2019 19:07:13 +0000
Labels: app=istio-pilot
chart=pilot-1.0.5
heritage=Tiller
istio=pilot
release=istio
Annotations: checksum/config-volume: f8da08b6b8c170dde721efd680270b2901e750d4aa186ebb6c22bef5b78a43f9
deployment.kubernetes.io/revision: 1
kubectl.kubernetes.io/last-applied-configuration:
{“apiVersion”:“extensions/v1beta1”,“kind”:“Deployment”,“metadata”:{“annotations”:{“checksum/config-volume”:"f8da08b6b8c170dde721efd680270b…
Selector: app=pilot,istio=pilot
Replicas: 1 desired | 1 updated | 1 total | 0 available | 1 unavailable
StrategyType: RollingUpdate
MinReadySeconds: 0
RollingUpdateStrategy: 1 max unavailable, 1 max surge

#2

This is sounds like resources limit issue. Minikube default memory is 2048 MB which is not enough for Istio. You need to have at least 4096 MB in order to get Istio components up and running. Try to restart Minikube with 4096 MB : minikube start --memory=4096 --disk-size=30g

#3

I am facing the same issue on kubernetes cluster on AWS. I followed the Quickstart and deployed the bookinfo application. But the istio-pilot pod remains in the pending state.

I checked the memory,disk pressure, and it is okay (no pressure).

Can anyone help me?

1 Like
#4

Same issue here… any ideas besides resource limit issue?