The conversation

pdimitarHNSource author
Lessons learnedExperience excerpt · English

Really? So when do I get to describe my singular app that needs Postgres and Kafka in 7-10 lines in …

… Really? So when do I get to describe my singular app that needs Postgres and Kafka in 7-10 lines in a .txt file and not {checks our company's ArgoCD backend repo} ... not 8 YAML files? I ain't got all day or a week, where is that? Nice declarative MINIMAL syntax with all the BS inferred for me (like names and stuff, why should I think of 5-10 names of stuff? Figure it out, automated tool!) that only concentrates on what is being deployed. It can generate everything else just fine, or at least it should, in a more sane world anyway. Excuse the slightly combative tone, I ain't trolling you here but you also come across as a bit blind about things outside the k8s holy land. > Once you have a bunch of components that implement this API, it becomes trivial to deploy pretty much any level of complexity Nope, nothing ever becomes trivial with k8s. I was on call with two senior platform engineers and we needed 3-4 hours to describe a single small app that needs Postgres and Kafka and to listen on a single port while needing a single env var and a few super small config files. …

Original discussionK8s Service Meshes: The Bill Comes Due239 source comments · at import
2

What was this responding to?

Parent context · original excerpt

GR
growseHN

I find it hard to believe that you've considered this for more than than two seconds and can't think of a single reason why k8s might be a good fit for someone's requirements. But here's one: It's a curated, extensible API that provides a decent abstraction over a heterogeneous collection of hardware. Nobody's done that before, and it's extraordinarily useful for being able to define intent . No-one forces you to use YAML, it's just a serialisation format. Once you have a bunch of components that implement this API, it becomes trivial to deploy pretty much any level of complexity of containerised application, without having to care too much about the actual exact details of how scheduling, networking, storage etc. is implemented. Even better, I can hit two different clusters configured in two completely different ways with the same manifest and get roughly the same result. It's the abstr…

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

VO
VolundrHN

> Really? So when do I get to describe my singular app that needs Postgres and Kafka in 7-10 lines in a .txt file Could you post those 7-10 lines needed to fully manage a Postgres AND Kafka deployment? I'm by no means a master, but I have a decent amount of experience outside the "k8s holy land" and I have no idea how to accomplish that.

Full original
GR
growseHN

shrug You originally said "I don't see how it's useful", and I observed that some people find it useful. I'm sorry you've had a bad experience, but it's a bit short-sighted to extrapolate from that to "this is universally useless". > you also come across as a bit blind about things outside the k8s holy land. You're not the only one with multiple decades of experience in writing code and managing infrastructure. I've used a lot of the tools in the toolbox, I know when each is likely to be more or less appropriate.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.