<p>Created a two node cluster with kubeadm. </p>

<p>Installed <strong>istio 1.1.11</strong></p>

<p><strong>kubectl version</strong></p>

<pre><code>Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:32:14Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
</code></pre>

<p>Executed the commands as given in istio documentation</p>

<p>$<code>for i in install/kubernetes/helm/istio-init/files/crd*yaml; do kubectl apply -f $i; done</code></p>

<p>$ <code>kubectl apply -f install/kubernetes/istio-demo.yaml</code></p>

<p>Services got created.</p>

<p>$ <code>kubectl get pods -n istio-system</code></p>

<p><strong>Telemetry and policy pod status turned to CrashLoopBackOff status</strong></p>

<pre><code>istio-policy-648b5f5bb5-dv5np                 1/2        **CrashLoopBackOff**      5          2m52s

istio-telemetry-57946b8569-9m7gd           1/2     **CrashLoopBackOff**   5          2m52s
</code></pre>

<p>While describing the pod, getting the following error</p>

<pre><code> Warning  FailedMount  2m16s (x2 over 2m18s)  kubelet, ip-xxx-xxx-xxx-xxx  MountVolume.SetUp failed for volume "policy-adapter-secret" : couldn't propagate object cache: timed out waiting for the condition
</code></pre>

<p>Tried restarting the VM, restarted docker service. It did not help.</p>

<p>Because of the above error, the pod repeatedly try to restart and then crash.</p>

<p>Need your help in resolving this</p>

<p>These Mixer services may be crashlooping if your node(s) don't have enough memory to run Istio. More and more, people use tools like <a href="https://meshery.layer5.io/docs/installation#platform-docker-" rel="nofollow noreferrer">Meshery</a> to install Istio (and other service meshes), because it will highlight points of contention like that of memory. When deploying either the <code>istio-demo</code> or <code>istio-demo-auth</code> configuration profiles, you'll want to ensure you have a <a href="https://meshery.layer5.io/docs/installation#platform-docker-" rel="nofollow noreferrer">minimum of 4GB RAM</a> per node (particularly, if the Istio control plane is only deployed to one node).</p>
