Not surprisingly, I disagree. Running code and writing it has never been more decoupled, for the better. Why should i care where my code is running? It needs traffic and a way to access a database. Doesn't matter if that is local or somewhere in the cloud - ThreadSky

fake51.bsky.social • 34 days ago

Not surprisingly, I disagree. Running code and writing it has never been more decoupled, for the better. Why should i care where my code is running? It needs traffic and a way to access a database. Doesn't matter if that is local or somewhere in the cloud

Comments

martindotnet.bsky.social•34 days ago

The idea of k8s (the part of k8s agree with) is that as an engineer, you should be able to describe the dependencies and capabilities your app requires (redis, postgres, etc.), and I like that you can do that in an agnostic language.

The part that I hate is k8s engineers having to maintain things.

fake51.bsky.social•34 days ago

Until the robot Overlords have taken over, some engineer will have to maintain infrastructure and its abstractions. If you hate it, pay someone else to do it. There is no magicking it away.

martindotnet.bsky.social•34 days ago

My argument is "someone else" doesn't need to be someone inside your organisation, on a longer term timeline.

Keep the k8s API (the parts that are dev focused), remove the k8s platform under the hood.

jauntywk.bsky.social•34 days ago

Are you aware of @kcp.io ? A Kubernetes control plane you can embed into all kinds of systems.
https://github.com/kcp-dev/kcp

fake51.bsky.social•34 days ago

Well, that's what cloud offered k8s, isn't it? Get your k8s from Google or MS, you don't have to maintain it. You don't even know how they provide it

martindotnet.bsky.social•34 days ago

Kind of?

In those scenarios, even with AKS Automatic and GKE co-pilot, people are still deploying certmanager, istio, and other tech that lives in the cluster.

I'm suggesting it's more like Azure Container Apps and cloud run, but with the k8s API and cost benefits.

fake51.bsky.social•34 days ago

That sounds unlikely. Someone has to maintain the dependencies and the infrastructure, they need to get paid on top of what k8s costs. And personally, i would never deliver a product that handled security and risks and then provide the customer an API to change it.

basil404.bsky.social•34 days ago

At the end of the day, the people writing code and the people ensuring it runs are working toward the same goal. Developers should care how their code is running, for the same reasons infrastructure people care what the code is doing. Decisions made on one side have impacts on the other.

fake51.bsky.social•34 days ago

I still disagree with your conclusions. How are you going to architect your code differently knowing that your code is running in k8s vs running on x VMs? As a platform engineer, why should the code architecture matter to you when deciding on upgrading underlying infrastructure?

fake51.bsky.social•34 days ago

I think the teams should work together and we should avoid silos. That is far from application developers needing to know about Kubernetes implementation details, or VM setups.

Comments

Posting Rules

Reply