<p>I tried to install ibm-eventstreams-dev v 0.1.2 into my Mac. </p>

<p>After I installed eventstreams into my Mac, there's always several pods that can't run. It includes three kafka pods: es-ibm-es-kafka-sts-0/1/2, es-ibm-es-ui-deploy-69758d9dfd-kc2zx, es-ibm-es-ui-oauth2-client-reg-pgvq6 and there also have a failed job named es-ibm-es-ui-oauth2-client-reg. </p>

<p>You can see the details in the follow images:
<a href="https://i.stack.imgur.com/Qg3MB.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Qg3MB.png" alt="enter image description here"></a></p>

<p><a href="https://i.stack.imgur.com/n3YpQ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/n3YpQ.png" alt="enter image description here"></a></p>

<p><a href="https://i.stack.imgur.com/h4ZBu.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/h4ZBu.png" alt="enter image description here"></a></p>

<p>So I have two questions about the ibm-event-stream:</p>

<ul>
<li><p>Does ibm-eventstreams-dev only supported on ICP? Can I install it on my local environment without ICP environment?</p></li>
<li><p>How could I solve the ui pods problem in the ibm-eventstreams-dev? </p></li>
<li><p>what's wrong with the kafka pods? what's the status message "CrashLoopBackOff" means?</p></li>
</ul>

<p>My environment details:</p>

<ul>
<li>kubernetes 1.11.1</li>
<li>helm : stable 2.10.0</li>
<li>a cluster have three nodes, each nodes is a virtual macine.</li>
</ul>

<p>Please help me, Thanks a lot!</p>

DoubleQueens
<p>ibm-eventstreams-dev will only work in ICP, it can not be installed into your local environment.</p>

<p>Assuming the above is from an ICP instance then I think there are two things to investigate:</p>

<ul>
<li><p>Take a look at the logs for the oauth2-client-reg job, as that should have run successfully to completion as part of the install, using kubectl logs, or the ICP UI.</p></li>
<li><p>CrashLoopBackOff means that a container in the Kafka pod is starting, then crashing, then starting, then crashing, and never managing to start.  Again, take a look at the logs, this time using kubectl logs to see the current logs and kubectl logs --previous to see the previous instance's logs, to get an understanding of why this is.</p></li>
</ul>
