Kubernetes for Developers Who Know How to Develop
1–10 of 106 posts
Re: Kubernetes for Developers Who Know How to Develop
#2> 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. Not exactly "Best Friends Forever". I wish people writing this kind of introductory blog posts would take the time and just quickly explain container runtimes instead of just mentioning docker and be done with it.
Re: Kubernetes for Developers Who Know How to Develop
#3> 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…
Does this apply to GKE? Are they going to remove support for Docker as well (or did they?)
Re: Kubernetes for Developers Who Know How to Develop
#4> 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…
While you are technically correct, kubernetes removed the Dockershim. Docker is often used as a synonym for containers. However, most of the things should still work [1].
[1]: https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-...
Re: Kubernetes for Developers Who Know How to Develop
#5> 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…
While you are technically correct, kubernetes removed the Dockershim. Docker is often used as a synonym for containers. However, most of the things should still work [1]. [1]: https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-...
I am very much aware of this, but that's exactly what I am arguing. Articles setting out to explain Kubernetes should not perpetuate the false equality of docker and containers.
Re: Kubernetes for Developers Who Know How to Develop
#6> 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…
Does this apply to GKE? Are they going to remove support for Docker as well (or did they?)
They have, with 1.24[1], following Kubernetes upstream. If you are an end user nothing is really going to change from this though, because docker produces container images that can be used in other container runtimes (and in fact, containerd is what powers docker underneath today anyway). But that's why it's so important to explain that containers != docker, otherwise "removing docker support" seems really scary.
[1] https://cloud.google.com/kubernetes-engine/docs/deprecations...
Re: Kubernetes for Developers Who Know How to Develop
#7Earlier quoted context omitted.
Does this apply to GKE? Are they going to remove support for Docker as well (or did they?)
They have, with 1.24[1], following Kubernetes upstream. If you are an end user nothing is really going to change from this though, because docker produces container images that can be used in other container runtimes (and in fact, containerd is what powers docker underneath today anyway). But that's why it's so important to explain that containers != docker, otherwise "removing docker support" seems really scary. [1]…
> 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 things.
Docker is really the best word to describe what people are thinking about it every day conversation. So much so that I think they are at risk of loose their trademark.
Re: Kubernetes for Developers Who Know How to Develop
#8What part makes this for developers and what are developers that don't know how to develop?
Re: Kubernetes for Developers Who Know How to Develop
#9Earlier quoted context omitted.
They have, with 1.24[1], following Kubernetes upstream. If you are an end user nothing is really going to change from this though, because docker produces container images that can be used in other container runtimes (and in fact, containerd is what powers docker underneath today anyway). But that's why it's so important to explain that containers != docker, otherwise "removing docker support" seems really scary. [1]…
> 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 required by Kubernetes. You can go through a third-party solution that adds CRI support on top of docker, but most managed Kubernetes offerings simply removed docker support.
I don't see any argument supporting the claim that docker is the "best word" to describe containers. I am also not aware of ambiguity for the term "(Linux) container" when it comes to operating/deploying software. What else does it mean in that context?
Re: Kubernetes for Developers Who Know How to Develop
#10Earlier quoted context omitted.
While you are technically correct, kubernetes removed the Dockershim. Docker is often used as a synonym for containers. However, most of the things should still work [1]. [1]: https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-...
I am very much aware of this, but that's exactly what I am arguing. Articles setting out to explain Kubernetes should not perpetuate the false equality of docker and containers.
If you use `docker build/run` in your bash, it will actually be more confusing IMO saying k8s "dropped docker(shim) support". This fact should be a footnote for the curious reader, surely on an introduction article.