3 ms·

100%. For the startup we're starting/working on now, we're running microk8s on bare metal (dedicated servers). What you describe is a big reason for it. Once y

100%. For the startup we're starting/working on now, we're running microk8s on bare metal (dedicated servers). What you describe is a big reason for it. Once you have k8s set up, services can be very easily deployed with auto TLS, and basic auth or oauth2 is really simple as well. So we're big believers in vertical scaling, but still use k8s (microk8s or k3s) for these kinds of benefits. An additional benefit of this is that it makes scaling/transitioning to a bigger/managed k8s easy down the road. It might sound like overkill, but it takes about 10 minutes to set up microk8s on a ubuntu lts server. It comes with nginx ingress. Install cert manager (another 5 mins) and you don't even need traefik these days. All configs are kept in Git.

mwcampbell 6y ago
Do you have any opinion on microk8s versus k3s?
toyg 6y ago
All these “it takes 10 minutes” should really be “it takes 10 minutes plus several hours/days/weeks actually learning how to run and maintain all this stuff”.
- cutemonster 6y ago
  Precisely. Some weeks reading, then 10 minutes doing (well some hours or a day doing, more likely). And then half a day downtime every now and then maybe? Until one knows enough about the new stack
chrisandchris 6y ago
I would even go to a lower level. I use Docker swarm and Docker compose. It is reliable, simple and very effective.
gofreddygo 6y ago
> it takes about 10 minutes After you've spent weeks / months reading blogs, installing dependencies, tweaking parameters, playing around deployments and figuring out new names for the same old stuff, debugging that extra whitespace in the yaml file only to figure out oww, you could use helm charts for deployments which is eerily similar to how jsp looked like 15 years ago and everything that was wrong with templating deployments than scripting it. Then it takes about 4 mins. And now you get to do brown bag sessions with your baffled team members! Yay! But only till kubernetes evicts your pods for being too resource "hungry". Gotta keep prod up folks. Better grab a coffee and kubectl ("kube-cuttle" is it?) into prod to check why the pods have restarted 127 times.

mwcampbell 6y ago

Do you have any opinion on microk8s versus k3s?

toyg 6y ago

All these “it takes 10 minutes” should really be “it takes 10 minutes plus several hours/days/weeks actually learning how to run and maintain all this stuff”.

cutemonster 6y ago
Precisely. Some weeks reading, then 10 minutes doing (well some hours or a day doing, more likely). And then half a day downtime every now and then maybe? Until one knows enough about the new stack

chrisandchris 6y ago

I would even go to a lower level. I use Docker swarm and Docker compose. It is reliable, simple and very effective.

gofreddygo 6y ago

> it takes about 10 minutes After you've spent weeks / months reading blogs, installing dependencies, tweaking parameters, playing around deployments and figuring out new names for the same old stuff, debugging that extra whitespace in the yaml file only to figure out oww, you could use helm charts for deployments which is eerily similar to how jsp looked like 15 years ago and everything that was wrong with templating deployments than scripting it. Then it takes about 4 mins. And now you get to do brown bag sessions with your baffled team members! Yay! But only till kubernetes evicts your pods for being too resource "hungry". Gotta keep prod up folks. Better grab a coffee and kubectl ("kube-cuttle" is it?) into prod to check why the pods have restarted 127 times.