SanndyTheManndy

joined 1 year ago
[–] SanndyTheManndy 1 points 38 minutes ago* (last edited 38 minutes ago) (1 children)

The Earth is 5 days old, since it has been 5 days since Thursday.

[–] SanndyTheManndy 10 points 1 day ago (1 children)

Mine can catch 2 mice at the same time. And also wasps, centipedes, lizards, pigeons, etc.

[–] SanndyTheManndy 8 points 2 days ago

Junji Ito having a braingasm rn

[–] SanndyTheManndy 3 points 4 days ago

Show, don't tell, innit

[–] SanndyTheManndy 2 points 5 days ago

Both are ways to manage containers, and both can use the same container runtime provider, IIRC. They are different in how they manage the containers, with docker/docker-compose being suited for development or one-off services, and kubernetes being more suitable for running and managing a bunch of containers in production, across machines, etc. Think of kubernetes as the pokemon evolution of docker.

[–] SanndyTheManndy 3 points 6 days ago

Getting around deep packet inspection.

[–] SanndyTheManndy 3 points 1 week ago (3 children)

Why did you not include DPI spoofing?

[–] SanndyTheManndy 3 points 1 week ago

You measure time on the scale of emergency to emergency.

[–] SanndyTheManndy 1 points 1 week ago (1 children)

I did come across it before, but it feels like just another layer of abstraction over k8s, and with a smaller ecosystem. Also, I prefer terminal to web UI.

[–] SanndyTheManndy 1 points 1 week ago

Setting up k8s with k3s is barely two commands. Works out of the box without any further config. Heck, even a multi-node cluster is pretty straightforward to setup. That's what we're using at work.

[–] SanndyTheManndy 4 points 1 week ago

Several services are interlinked, and I want to share configs across services. Docker doesn't provide a clean interface for separating and bundling network interfaces, storage, and containers like k8s.

view more: next ›