Convert Docker Compose Files to Kubernetes Manifests with Kompose

Docker Compose make it easy to spin up local development environment with all of application dependencies using a single Compose file. However, when we want to run the same application on Kubernetes, we normally need Kubernetes configuration files such as, deployment, service, etc. In this blog we’ll explore how Kompose works, how to use it to generate Kubernetes configurations from an existing Compose file, and what you should review or modify before deploying the generated manifests to a Kubernetes cluster.

Pre-requisites:

• Docker installed
• Kind installed
• kubectl installed
• An existing Docker Compose file for the application

Exposing Kafka from kind to a Local Windows Application

In our previous blog post, we discussed a workaround for the DNS error that occurs when an application running on a local Windows machine connects to Kafka. In this post, we will discuss the proper solution.

Our Kafka cluster runs inside Docker through a local kind Kubernetes cluster rather than directly on the host machine. Kafka advertises broker addresses using Kubernetes DNS names, which can be resolved from inside the cluster but not by an application running on Windows. To make Kafka reachable from the host, we must expose the required ports from the kind node container to the host machine.