Our great sponsors
-
compose-on-kubernetes
Discontinued Deploy applications described in Compose onto Kubernetes clusters
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
enjoy the title says, https://github.com/docker/compose-on-kubernetes is no longer maintained, with no explanation why and no recommendations on what to use instead. i've briefly looked at Kompose as an alternative, but i don't like how it's a converter. i'd prefer the source of truth to exist inside a single, simpleYAML file, like a docker-compose file. what would you recommend?
You can use kind (https://github.com/kubernetes-sigs/kind) to run local kubernetes clusters and combine it with yaml manifests, helm charts, kustomize or carvel packages. Depending on your workflow and tooling.
Docker swarm was introduced to plug this deficiency and allow docker-compose to treat a pool of VMs as one large computer. In practice we found early versions of Docker Swarm didn't work particularily well, especially when the number of nodes went above 10 and stuff like load balancers and scaling became hard to do in a single compose file.... in short this stuff is hard to do at scale. To give credit, docker swarm introduced a new concept of "stacks", but this introduced incompatible changes to the docker compose syntax, which in my companies case marooned us on docker compose v2.....
To conclude I think the Compose-on-Kubernetes folks gave up due to poor adoption. I don't condemn sometimes a genius idea like Fig runs its course. If you are alergic to the K8s API (YAML), that's fine because it was never designed to be written by humans. I would direct you instead to Kubevela, a k8s implementation of the OAM specification. OAM is designed to describe an Application and have that translated to the underlying platform.