<p>I want to run Eventstore in Kubernetes node. I start the node with <code>minikube start</code>, then I apply this yaml file:</p>

<pre><code>apiVersion: apps/v1
kind: Deployment
metadata:
  name: eventstore-deployment
spec:
  selector:
    matchLabels:
      app: eventstore
  replicas: 1
  template:
    metadata:
      labels:
        app: eventstore
    spec:
      containers:
      - name: eventstore
        image: eventstore/eventstore
        ports:
        - containerPort: 1113
          protocol: TCP
        - containerPort: 2113
          protocol: TCP
---
apiVersion: v1
kind: Service
metadata:
  name: eventstore
spec:
  selector:
    app: eventstore
  ports:
  - protocol: TCP
    port: 1113
    targetPort: 1113
---
apiVersion: v1
kind: Service
metadata:
  name: eventstore-dashboard
spec:
  selector:
    app: eventstore
  ports:
  - protocol: TCP
    port: 2113
    targetPort: 2113
    nodePort: 30113
  type: NodePort
</code></pre>

<p>the deployment, the replica set and the pod starts, but nothing happens: Eventstore doesn't print to the log, I can't open its dashboard. Also other services can't connect to <em>eventstore:1113</em>. No errors and the pods doesn't crash.
The only I see in logs is "The selected container has not logged any messages yet".</p>

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

<p>I've tried a clean vanilla minukube node with different vm drivers, and also a node with configured Ambassador + Linkerd. The results are the same. </p>

<p>But when I run Eventstore in Docker with this yaml file via <em>docker-compose</em></p>

<pre><code>eventstore:
    image: eventstore/eventstore
    ports:
      - '1113:1113'
      - '2113:2113'
</code></pre>

<p>Everything works fine: Eventstore outputs to logs, other services can connect to it and I can open its dashboard on 2113 port.</p>

<p><strong>UPDATE:</strong> Eventstore started working after about 30-40 minutes after deployment. I've tried several times, and had to wait. Other pods start working almost immediately (30 secs - 1 min) after deployment. </p>

ligowsky
<p>As @ligowsky confirmed in comment section, issue was cause due to VM Performance. Posting this as Community Wiki for better visibility. </p>

<p><code>Minikube</code> as default is running with <code>2 CPUs</code> and <code>2048 Memory</code>. More details can be found <a href="https://github.com/kubernetes/minikube/blob/232080ae0cbcf9cb9a388eb76cc11cf6884e19c0/pkg/minikube/constants/constants.go#L103" rel="nofollow noreferrer">here</a>.</p>

<p>You can change this if your VM has more resources.</p>

<p><strong>- During Minikube start</strong></p>

<pre><code>$ sudo minikube start --cpus 2 --memory 8192 --vm-driver=&lt;driverType&gt;
</code></pre>

<p><strong>- When Minikube is running, however minikube need to be restarted</strong></p>

<pre><code>$ minikube config set memory 4096
⚠️  These changes will take effect upon a minikube delete and then a minikube start
</code></pre>

<p>More commands can be found in <a href="https://minikube.sigs.k8s.io/docs/examples/" rel="nofollow noreferrer">Minikube docs</a>.</p>

<p>In my case when <code>Minikube</code> resources was 4CPUs and 8192 memory I didn't have any issues with <code>eventstore</code>.</p>

<p><strong>OP's Solution</strong></p>

<p>OP used <a href="https://github.com/kubernetes-sigs/kind" rel="nofollow noreferrer">Kind</a> to run <code>eventstore</code> deployment. </p>

<blockquote>
  <p>Kind is a tool for running local Kubernetes clusters using Docker
  container "nodes". kind is primarily designed for testing Kubernetes
  1.11+</p>
</blockquote>

<p><code>Kind</code> documentation can be found <a href="https://kind.sigs.k8s.io/docs/user/quick-start/" rel="nofollow noreferrer">here</a>.</p>
