<p>I am quite new to <code>Kubernetes</code> and I have been struggling to migrate my current <em>docker-compose</em> environment to Kubernetes...</p>
<p>I converted my <code>docker-compose.yml</code> to Kubernetes manifests using <strong>kompose</strong>.</p>
<p>So far, I can access each pod individually but it seems like I have some issues to get those pods to communicate each other.. My Nginx pod can not access my app pod</p>
<p>My <code>docker-compose.yml</code> is something like below</p>
<pre><code>version: '3.3'
services:

  myapp:
    image: my-app
    build: ./docker/
    restart: unless-stopped
    container_name: app
    stdin_open: true
    volumes:
      - mnt:/mnt
    env_file:
      - .env


  mynginx:
    image: nginx:latest
    build: ./docker/
    container_name: nginx
    ports:
      - 80:80
    stdin_open: true
    restart: unless-stopped
    user: root
</code></pre>
<p>My <code>Nginx.conf</code> is something like below</p>
<pre><code>server{
    listen 80;
    index index.html index.htm;
    root   /mnt/volumes/statics/;


location /myapp {

  proxy_pass http://myapp/index;

  proxy_redirect     off;
  proxy_set_header   Host $host;
  proxy_set_header   X-Real-IP $remote_addr;
}
</code></pre>
<p>I understand that <code>docker-compose</code> enables containers to communicate each other through service names (<strong>myapp</strong> and <strong>mynginx</strong> in this case). Could somebody tell me what I need to do to achieve the same thing in Kubernetes?</p>

rks
<p>Kompose did create services for me. It turned out that what I missed was docker-compose.overwrite file (apparently kompose just ignores overwrite.yml).</p>
