What part makes this for developers and what are developers that don't know how to develop?
Probably a joke for all those software engineers that don’t do anything.
Kubernetes for Developers Who Know How to Develop
11–20 of 106 posts
Re: Kubernetes for Developers Who Know How to Develop
#12What part makes this for developers and what are developers that don't know how to develop?
I've read through twice and I cannot see the relationship between the title and the contents.
Re: Kubernetes for Developers Who Know How to Develop
#13What part makes this for developers and what are developers that don't know how to develop?
I've read through twice and I cannot see the relationship between the title and the contents.
It's the part where it explains the "what" and "why" but skips the "how" under the assumption someone who knows how to develop just needs a hook to relate it to what they already know, and can then learn on their own.
Re: Kubernetes for Developers Who Know How to Develop
#14Kubernetes was a clever ploy to trick cloud providers into abstracting themselves into irrelevance, but otherwise a dead end. Can we please hurry up and replace it with an open-source Nomad clone?
Re: Kubernetes for Developers Who Know How to Develop
#15I’ve been working on a Kubernetes cluster for my home network. I know a lot of people hate on Kubernetes, but it’s pretty cool and not too bad to even get started from scratch with Kubeadm.
I think the constant thought in the back of my mind is… Docker containers and Nginx is definitely enough for my needs. At work, it’s a different story, but more most things, it can be over kill.
Re: Kubernetes for Developers Who Know How to Develop
#16> Kubernetes x Docker: Best Friends Forever > Whenever you hear Kubernetes, you’re probably going to hear Docker in the same sentence. Kubernetes and Docker are like peanut butter and jelly—they’re a perfect pair. For what it's worth, this article was originally written in October 2021, but even at that point it was clear that Kubernetes would remove support for docker. In fact it has already with Kubernetes 1.24. No…
> remove support for docker
So I can't use Dockerfiles and `docker build` to build things for k8s?
Re: Kubernetes for Developers Who Know How to Develop
#17I'm going to post my unsolicited opinion about K8s here, as an SWE+SRE who used it heavily for about 1.5 years on GCP.
It's a very cool system. I completely understand why people half-jokingly call it a "distributed operating system." It does a lot of things related to the lifecycles of various state (secrets, storage, config, deployments, etc).
However, I believe it goes way too far into putting infrastructure into non-cloud-managed state machines. Things that exist in most modern clouds are being reinvented in K8s. What's more, is that K8s objects are being created as interfaces to the underlying cloud objects. So you now have 2 layers of abstractions, each with their own quirks. It's too much.
Not to mention that IaC for K8s is extremely immature. This will improve, yes, for some definition of "improve." But if you've ever written Helm charts that integrate with Terraform, you'll know about all the spinning plates you have to keep balanced.
It's not a system I see sustaining into the long term future. Google may continue to use and support it forever, but afaik, they are the most invested in its success. Other cloud platforms, like AWS, seem to be focusing on not re-inventing all of their cloud offerings in K8s.
Re: Kubernetes for Developers Who Know How to Develop
#18Why does everyone keep thinking developers need to now about K8S? Just be glad if your infra/DevOps/platform teams abstract this away from you and you don't have to deal with this insanity.
Re: Kubernetes for Developers Who Know How to Develop
#19Why does everyone keep thinking developers need to now about K8S? Just be glad if your infra/DevOps/platform teams abstract this away from you and you don't have to deal with this insanity.
Not every org delegates these responsibilities to separate roles.
Re: Kubernetes for Developers Who Know How to Develop
#20Earlier quoted context omitted.
> They have The question was did they remove support for docker. They have not. They simply removed dockershim and no longer special case it. Your point is that we should stop using a brand name to describe OCI open standard containers. However, like aspirin, the names are interchangable for the vast majority of people. OCI container doesn't really roll off the toung, and container by itself could mean all sorts of t…
> The question was did they remove support for docker. They have not. Have they not? Note that the GP asked for GKE specifically. The support page I linked to literally says so: > GKE will stop supporting node images that use Docker as the runtime in GKE version 1.24 and later Removing dockershim removed the existing support for docker, because docker does not support CRI (Container Runtime Interface), the API requir…
Saying "Kubernetes has removed support for Docker" is incredibly misleading at best, and less charitably, is just plainly wrong.
While it's true that 1.24 does not support docker as the specific container runtime that's directly used by Kubernetes itself, this has approximately zero impact on how the vast majority of beginners would use Kubernetes, as out of the box you're still able to run docker containers.
Probably not the kind of confusing detail that needs to be in an intro to Kubernetes article.