> thousands of monitoring checks per minute That isn’t a lot. You could easily run that from one host. The reason people reach for Kubernetes (and similar) is because they need to scale past that single host dependency.
..and HA
Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
11–20 of 81 posts
Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
#12> thousands of monitoring checks per minute That isn’t a lot. You could easily run that from one host. The reason people reach for Kubernetes (and similar) is because they need to scale past that single host dependency.
The reason most people reach for Kubernetes is because it's cool. The entire infra the vast majority of Kubernetes users have could run on a single bare metal machine with a second one for redundancy. To be fair: using Kubernetes anyways builds the skill just in case you become one of the 0.1% who actually need it down the line.
You can hire an Azure or Google Kubernetes devops guy and he will be equally comfortable on your AWS EKS kubernetes cluster. And when he leaves, you don't have a six week onboarding process with the new guy to learn all the ins and outs of your totally bespoke, non-standard container orchestration system that was cobbled together by two devs with no operations experience.
K3S takes about 5 minutes to setup the first time and you instantly have an entire universe of standardized operational tooling. I wouldn't touch docker compose with a 20 foot pole for production work.
Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
#13[deleted]
Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
#14> thousands of monitoring checks per minute That isn’t a lot. You could easily run that from one host. The reason people reach for Kubernetes (and similar) is because they need to scale past that single host dependency.
You could, but they don't, meaning their argument is still sound (whether they _could_ use a single host is besides the point, they're not doing that).
Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
#15> thousands of monitoring checks per minute That isn’t a lot. You could easily run that from one host. The reason people reach for Kubernetes (and similar) is because they need to scale past that single host dependency.
The reason most people reach for Kubernetes is because it's cool. The entire infra the vast majority of Kubernetes users have could run on a single bare metal machine with a second one for redundancy. To be fair: using Kubernetes anyways builds the skill just in case you become one of the 0.1% who actually need it down the line.
As soon as you work in a team, it’s irrelevant whether the project actually needs it. There will be someone who convinces stakeholders that it is necessary and then you just have to fall in line and learn the skills knowing that it is most likely one of the 99.9% of projects where it is just overkill.
Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
#16Earlier quoted context omitted.
The reason most people reach for Kubernetes is because it's cool. The entire infra the vast majority of Kubernetes users have could run on a single bare metal machine with a second one for redundancy. To be fair: using Kubernetes anyways builds the skill just in case you become one of the 0.1% who actually need it down the line.
You can hire an Azure or Google Kubernetes devops guy and he will be equally comfortable on your AWS EKS kubernetes cluster. And when he leaves, you don't have a six week onboarding process with the new guy to learn all the ins and outs of your totally bespoke, non-standard container orchestration system that was cobbled together by two devs with no operations experience. K3S takes about 5 minutes to setup the first…
Docker compose is hardly "totally bespoke".
Setting up K8s isn't rocket science, but maintaining it are offputting, to say the least.
Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
#17Are you monitoring resource utilization per container? Do notifications get sent out when container(s) become unhealthy? How are you handling secrets?
These are things I'm trying to figure out at work using Podman. Would love to hear about any experience in these areas.
Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
#18so op just recreated with sticks and tape a very basic feature what k8s does out of the box, and nobody else would be able to support his creation, because its handrolled adhoc with sparse documentation.
sounds like ghetto engineering
Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
#19> thousands of monitoring checks per minute That isn’t a lot. You could easily run that from one host. The reason people reach for Kubernetes (and similar) is because they need to scale past that single host dependency.
The reason most people reach for Kubernetes is because it's cool. The entire infra the vast majority of Kubernetes users have could run on a single bare metal machine with a second one for redundancy. To be fair: using Kubernetes anyways builds the skill just in case you become one of the 0.1% who actually need it down the line.
> The reason most people reach for Kubernetes is because it's cool.
This shittake was probably valid 10y ago, I would have agreed with you back then
> The entire infra the vast majority of Kubernetes users have could run on a single bare metal machine
Where are you pulling this out of? A large number of k8s users don't need it, but the alternative you have sounds hyperbolic.
Re: Zero-Downtime Deployments with Docker Compose – No Kubernetes Required
#20> There's a mass delusion in the industry that you need Kubernetes to run a serious production service. You don't. At StatusDude, we serve thousands of monitoring checks per minute, run multi-region workers, and deploy multiple times a day This is pretty small scale, Kubernetes comes in when you've got a larger workload.
The whole reasoning behind this is flawed.
“We don’t know how to scale Traefik so we went with haproxy”
Well doh. Haproxy is designed for this. You can make haproxy serve copious amount of traffic on a single arm core and a little bit of ram. Imagine what you can do with a few replicas on your large clusters.
This has nothing to do with the choice of CI/CD or docker versus kubernetes.