- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
To be fair Kubernetes creates copies of the things it drops into the ocean to replace them as fast as they’re lost.
Kubernetes is more stable than docker compose. Docker compose is fishing for containers after the ship capsized. Frustrating and nothing works out of the box.
Huh? All my docker compose projects work fine ‘out of the box’, the oldest ones have been stable for years now.
Docker Compose brought “works on my machine” to the cloud.
I personally really enjoy interacting with docker compose and I’ve successfully used docker compose to get a 0 downtime setup on my company’s internal web servers by using a reverse proxy
I’d say that docker compose also has the containers strapped together with holes cut in the walls between them for communication.
Kubernetes is more the crane that stacks the containers onto passing ships instead of a singular ship itself.
Seriously! There’s no network, NAT, port forwarding, network isolation - hell, not even any iptables rules in any of these images. This meme makes no fucking sense.
almost as bad as kubernetes.
Suddenly, thousands of sneakers wash ashore all over Ireland and everybody is trying to pair them up.
Now add VMs and proxmox
The ocean is fake
ECS/EKS: The ocean belongs to someone else.
Each container sk8s right off the deck.
Talos Linux solves this.
???
Looks like I gotta new rabbit hole to jump down tonight
If replacing an existing server, make sure to wipe the disk during install.
Talos is great
Is it production-ready?
I’m thinking of setting it up on an OVH bare metal dedicated server to run various sites and Docker processes, but I don’t want to handle Kubernetes myself.
You always have to manage kubernetes. And talos is nothing but a ready to do k8s os.
If you don’t want kubernetes I’d suggest something like fedora coreos.
I’m ok with k8s, I’m just chicken shit because I’ve never had an opportunity to use them in prod.
How does Talos differ from something like Ubuntu with microk8s?
The only way to interact with it is using talosctl (no ssh, very minimal console, etc.) It is pretty slim and designed only to use k8s. Ubuntu on the other hand is general purpose that can be made to use k8s.
Basically the idea being that your nodes are also cattle.
It’s very interesting. I’m debating moving from fedora coreos to it. About to spin up a test cluster whenever I have free time.
I was aware of kubernetes 6 months ago, but had never used it.
I got a 3 node cluster running in a day, and was learning kubernetes.
The only issues I’ve had were due to hardware failure causing etcd instability, and misconfigured operators generating terabytes of logs leading to pod eviction.I don’t know what would signify it being production ready. It had all the levers and knobs I needed. I haven’t yet needed to run a sysadmin debug container to poke around the host OS.
It’s also great for learning. If you make a mistake, it’s very easy to wipe and reinstall and get back to where you were.
Where is openshift in this?
The ship is painted red and a few containers are bolted to it, rather than use provided.
Don’t forget the exorbitant fees by Red Hat.
If you use much of the software that is included in the support package, then the price seems reasonable. No way you could get the same price if you went to each provider individually. If all you use is bare bones openshift, then you’re right.
This is the most accurate description I can think of.