Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kafka-cron minor note about kompose #208

Merged
merged 1 commit into from
May 21, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions projects/kafka-cron/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -264,6 +264,8 @@ Follow the steps to install the program and run the `hello-minikube` application
Once you have done this, you will need to convert your `docker-compose.yml` files to `kubernetes` deployment files.
There is a tool, [kompose](https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/) which may assist you.

> **Note:** `kompose` *will not* give you perfect results, however. In particular, `kompose` will not correctly convert cases where you are using a `docker-compose` `volume` to map a configuration file into your running container. `kompose` will just create a `persistentVolumeClaim` with empty data. The best thing to do is to remove those and use a [ConfigMap] for the config file content and map that in as a volume. You'll have to do this by hand. Note that there are some `persistentVolumeClaims` for application data that are appropriate - don't remove these, only the ones that are substituted for config.
Test that your system works as it did on `docker-compose`.

Learn your way around the `kubernetes` command-line tool, `kubectl` (see the [kubectl documentation](https://kubernetes.io/docs/reference/kubectl/)).
Expand Down
Loading