News for hackers. Stuff that matters.
Re:“Let’s use Kubernetes.” Now you have eight problems by shusson on Thursday March 05, 2020 @10:47AM (#22494520)
> I could never run a scalable service on the cloud without Kubernetes

Can you give us an indication of the scale of your app? e.g rpm.

Re:“Let’s use Kubernetes.” Now you have eight problems by flowerlad on Thursday March 05, 2020 @10:59AM (#22494658)
It is still in development, so no rpm at the moment.

That’s another thing: some people think Kubernetes is something you use if you need high scalability. I disagree. Kubernetes should be the default if your app consists of more than 1 service. If you don’t have high scalability requirements you can rent a single-node GKE “cluster” for about $60 per month.

If you have just 1 service then a single Docker container is all you need, so Kubernetes not needed.

Re:“Let’s use Kubernetes.” Now you have eight problems by EpicEng on Thursday March 05, 2020 @01:19PM (#22496344)
This mentality is how we end up with overly engineered piles of dung. Instead of building something in the most simple way practical which would fulfill our requirements, we go all out. Now changing things takes longer because to do anything you have to weave through 10+ layers of opaque abstraction. No thanks.
Re:“Let’s use Kubernetes.” Now you have eight problems by regularfry on Thursday March 05, 2020 @11:30AM (#22495010)
If you don't have high scalability requirements, virtually anything will work. You're probably paying $55/month over the odds.
Re:“Let’s use Kubernetes.” Now you have eight problems by petilon on Thursday March 05, 2020 @11:40AM (#22495155)
What will you use for service discovery?
Re:“Let’s use Kubernetes.” Now you have eight problems by JackRabbitSlim on Thursday March 05, 2020 @12:54PM (#22496069)
off the top of my head?

a) Shared data source; each service writes pid/state to a file in the shared data store. It could be a single directory in a single server setup or a dedicated NFS/SMB server for hundreds/thousands of nodes.

b) Pub/Sub service; Kafka, et al, in which services simply subscribe to and publish to a central channel to see everyone else.

c) Determinism; You use predictable naming/addressing and simply infer. This is tricky to scale but not impossible.

d) Any number of stand alone discovery services ala Zookeeper or Eureka. They all end up being effectively the same pub/sub model as B, just prepackaged.

e) You don't discover shit, you have a single load balanced endpoints that can scale out instances as needed behind balancer with zero knowledge required by the rest of the system.

Pick one to suit your needs. Service Discovery is not that hard and has been way over engineered.

Re:“Let’s use Kubernetes.” Now you have eight problems by mcbutterbunz on Thursday March 05, 2020 @01:43PM (#22496625)
As I was reading this, I thought to myself "How does this scale" and then I re-read the parent comment that said "If you don't have high scalability requirements, virtually anything will work."

The fact of the matter is that Kubernetes solves certain problems well but also presents other problems/challenges. For some organizations, the problems K8s solves is bigger than the problems/challenges it creates. It's all about trade offs.

Some people do want to hop on the next big thing in order to keep their imposter syndrome in check. Others know a certain technology and stick with it.

Sorry, I'm just ranting.

Re:“Let’s use Kubernetes.” Now you have eight problems by flowerlad on Thursday March 05, 2020 @04:06PM (#22498251)
There are lots of ways to avoid learning Kubernetes, but why? Kubernetes is so well designed and easy to learn and use!
Re:“Let’s use Kubernetes.” Now you have eight problems by skibbityboop on Friday March 06, 2020 @04:28PM (#22507485)
This is the comment you see from people on EKS or GKE. Many companies have compelling reasons to keep a large part, or all, of their services in-house. Nobody who actually has to install and administer K8s is on here commenting about how easy it is to run, maintain, and upgrade on their bare metal hosts. Troubleshoot, I almost forgot troubleshoot! All of those moving pieces, and something is hosed at 3am. This will be fun.

It will be great if that changes someday, and there's certainly been progress, but for places where they'd need to run it themselves, K8s is a tough proposition.

Re:“Let’s use Kubernetes.” Now you have eight problems by james_s_tayler on Thursday March 05, 2020 @04:52PM (#22498747)
I took the time to learn it, and for just my side projects it's a ridiculous amount of overkill.
Re:“Let’s use Kubernetes.” Now you have eight problems by aganame on Thursday March 05, 2020 @11:51PM (#22501073)
/s
Re:“Let’s use Kubernetes.” Now you have eight problems by servercobra on Thursday March 05, 2020 @11:58AM (#22495399)
If you're not worrying about scalability like the OP said, static configs. Add a new service? Roll out config changes. Server goes down? Let the redundancy handle it, roll out config changes in the morning.
Re:“Let’s use Kubernetes.” Now you have eight problems by yxhuvud on Thursday March 05, 2020 @12:59PM (#22496127)
If you are a single dev writing of couple of small services all by yourself, then the odds are you don't need a technical solution for service discovery.
Re:“Let’s use Kubernetes.” Now you have eight problems by mrits on Thursday March 05, 2020 @11:07AM (#22494745)
Your comment makes me so irrationally angry. I totally disagree. But I'll be civil.

I write scalable apps without K8. I moved away from it. Stateless services are trivial to scale.

[dead]
Re:“Let’s use Kubernetes.” Now you have eight problems by EpicEng on Thursday March 05, 2020 @01:50PM (#22496699)
Most of us have to deal with the design decisions made by others. I can see how poor decisions can make someone angry down the road.
Re:“Let’s use Kubernetes.” Now you have eight problems by mrits on Thursday March 05, 2020 @01:22PM (#22496380)
That's exactly what my therapist said.
Re:“Let’s use Kubernetes.” Now you have eight problems by james_s_tayler on Thursday March 05, 2020 @04:38PM (#22498628)
It was probably more the "if you have more than 1 service you need Kubernetes".

No. You don't.

Re:“Let’s use Kubernetes.” Now you have eight problems by merb on Thursday March 05, 2020 @11:07AM (#22494742)
well if you have 1 service k8s is already useful. try to make blue/green or any other no downtime deployment. especially with database changes.

in k8s deployments are deterministic, it will roll out X containers at once (X is configurable and defaults to 1)