kompose VS alliance-auth-kubernetes

Install Kompose - a conversion tool that allows you to convert your Docker Compose code to Kubernetes configuration files Run kompose convert in the same directory as your docker-compose.yml to generate the config files for your Kubernetes cluster

Kubernetes (via kompose)

As stated on their homepage, with Kompose, you can now push the same file to a production container orchestrator!. The tool definitely covers a wide range of Kubernetes features, among which these are meaningless locally but crucial for kubernetes :

deploy: stage: deploy image: alpine/k8s:1.29.1 variables: NAMESPACE: $CI_COMMIT_REF_SLUG before_script: # init namespace - kubectl config use-context $KUBE_CONTEXT - kubectl create namespace $NAMESPACE || true # download tools - curl --show-error --silent --location https://github.com/stern/stern/releases/download/v1.22.0/stern_1.22.0_linux_amd64.tar.gz | tar zx --directory /usr/bin/ stern && chmod 755 /usr/bin/stern && stern --version - curl --show-error --silent --location https://github.com/kubernetes/kompose/releases/download/v1.32.0/kompose-linux-amd64 -o /usr/local/bin/kompose && chmod a+x /usr/local/bin/kompose && kompose version # show logs asynchronously. Timeout to avoid hanging indefinitely when an error occurs in script section - timeout 1200 stern -n $NAMESPACE "app-" --tail=0 --color=always & # in background, tail new logs if any (current and incoming) pod with this regex as name - timeout 1200 kubectl -n $NAMESPACE get events --watch-only & # in background, tail new events in background script: # first delete CrashLoopBackOff pods, polluting logs - kubectl -n $NAMESPACE delete pod `kubectl -n $NAMESPACE get pods --selector app.kubernetes.io/component=$MODULE | awk '$3 == "CrashLoopBackOff" {print $1}'` || true # now deploying - kompose convert --out k8s/ - kubectl apply -n $NAMESPACE -f k8s/ - echo -e "\e[93;1mWaiting for the new app version to be fully operational...\e[0m" # waiting for successful deployment - kubectl -n $NAMESPACE rollout status deploy/app-db - kubectl -n $NAMESPACE rollout status deploy/app-back - kubectl -n $NAMESPACE rollout status deploy/app-front # on any error before this line, the script will still wait for these threads to complete, so the initial timeout is important. Adding these commands to after_script does not help - pkill stern || true - pkill kubectl || true after_script: # show namespace content - kubectl config use-context $KUBE_CONTEXT - kubectl -n $NAMESPACE get deploy,service,ingress,pod

K3s is a small, open source, no nonsense, distribution of Kubernetes. I think you'll find it just as easy to setup as Swarm. The challenge will be that Kubernetes has an entirely different API compared to Docker/Docker Compose. This can be mitigated by a tool called kompose, but using this will limit what you can do on Kubernetes.

Although I recently moved my own services from docker compose to kubernetes using https://kompose.io/ and now the only thing I run with docker compose, currently, is my private docker registry but everything including in kube, are always in their own folders.

I haven't run into the need to do that, but there is the Kompose project that exists to help with the conversion (https://kompose.io/)!

Compose claims to do that. https://kompose.io and https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/

There’s a full docker config in the repo and a kubernetes example here (not updated in a while but still relevant, just swap out the container stuff) https://github.com/mckernanin/alliance-auth-kubernetes. Seat is really bloated and most groups of any size end up needing at least 4gb of ram to run seat.