reco-model-monitoring
kompose
Our great sponsors
reco-model-monitoring | kompose | |
---|---|---|
1 | 50 | |
3 | 9,145 | |
- | 1.6% | |
0.0 | 9.0 | |
over 2 years ago | 7 days ago | |
Python | Go | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
reco-model-monitoring
-
Converting docker-compose to yaml's issue
docker-compose
kompose
-
Can I scale my dockerized Flask solution with 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
-
One Minute: Compose
Kubernetes (via kompose)
-
☸️ Kubernetes: From your docker-compose file to a cluster with 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
-
Single docker compose stack on multiple hosts. But how?
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.
-
Should I be using a unified Docker-Compose.yml?
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.
- Podman Desktop v1.5 with Compose onboarding and enhanced Kubernetes pod data
- Reasons to Drop Docker for Podman
-
Podman Desktop 1.2 Released: Compose and Kubernetes Support
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/)!
-
If I pull a docker image, can that image file be uploaded to a kubernetes cluster and it will work right away?
Compose claims to do that. https://kompose.io and https://kubernetes.io/docs/tasks/configure-pod-container/translate-compose-kubernetes/
What are some alternatives?
coolify - An open-source & self-hostable Heroku / Netlify / Vercel alternative.
skaffold - Easy and Repeatable Kubernetes Development
rexray - REX-Ray is a container storage orchestration engine enabling persistence for cloud native workloads
nuclio - High-Performance Serverless event and data processing platform
python-flask-sample-app - Dockerized Python Flask Example application
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
alliance-auth-kubernetes
pack - CLI for building apps using Cloud Native Buildpacks
Flynn - [UNMAINTAINED] A next generation open source platform as a service (PaaS)
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
C4-PlantUML - C4-PlantUML combines the benefits of PlantUML and the C4 model for providing a simple way of describing and communicate software architectures
kubevela - The Modern Application Platform.