>These pieces were bolted on later, as an after thought.
First, I don't know why you think this? Moreover, what is the practical implications of the claim? Have you ever had a problem with DNS service discovery in a Kubernetes cluster? Or else what is the point of bringing this up at all? (Nor does this change the inaccuracy of the other claims)
>Many people have been forced into docker for a few years already, facing a ton of critical features that are completely missing. kube is a brand new project that only started to be usable recently, you seem to not take that into account.
It's been 1.0 for well over a year and I still don't know what you're getting at in regards to docker. Kubernetes is (more or less) powered by Docker (at least historically, it's getting to a point where the container runtime is pluggable via CRI/CRI-O).
>It doesn't help that marketing around containers is "over promise and under deliver".
Also no idea what this means. Kubernetes and containers have done everything I've expected them to do. I usually see this comment from people who haven't actually ever used them for more than a day and gleefully point to articles talking about stale docker images with vulnerabilities, ignoring that nearly the exact same problem happens with naive VMs + CM deployment methodologies. Or otherwise think they're magic, when they're not.
Not seeing anything to change my initial conclusion here.
Judging by the comment. You're the one who used Docker for a day or on nothing critical. Maybe you're also lucky to have started with Kubernetes, maybe even fully managed on Google Cloud.
I used it for 3 years at different companies with more or less hassle. The route to container has been full of dangers.
>You're the one who used Docker for a day or on nothing critical.
Not really, but thanks for coming for me instead of offering any substance beyond hand waving.
>Maybe you're also lucky to have started with Kubernetes, maybe even fully managed on Google Cloud.
I mean, sure, I think it's crazy to try to use Docker in Prod without an orchestrator and don't think Swarm Mode is mature enough for such a use case. And no, I don't use GKE.
Now that we've dropped anything that was really being discussed, let me agree with you, Docker itself is not my favorite, but that has nothing to do with containers or orchestrators in general and instead has to do with the QA of Docker and the frequency of breaks and regressions.
We both agree that orchestration is critical. Yet orchestrators are fairly new, the docker hype was strong long before they were viable, or existed at all.
You'll forgive me but implying that one one should just use an orchestrator points to one ignoring their history -or lack thereof-.
I have seen entire clusters taken out by a regression. Sadly, even the best orchestration cannot do much better than the core it is running on. You can google "docker in production" to get more substance.
First, I don't know why you think this? Moreover, what is the practical implications of the claim? Have you ever had a problem with DNS service discovery in a Kubernetes cluster? Or else what is the point of bringing this up at all? (Nor does this change the inaccuracy of the other claims)
>Many people have been forced into docker for a few years already, facing a ton of critical features that are completely missing. kube is a brand new project that only started to be usable recently, you seem to not take that into account.
It's been 1.0 for well over a year and I still don't know what you're getting at in regards to docker. Kubernetes is (more or less) powered by Docker (at least historically, it's getting to a point where the container runtime is pluggable via CRI/CRI-O).
>It doesn't help that marketing around containers is "over promise and under deliver".
Also no idea what this means. Kubernetes and containers have done everything I've expected them to do. I usually see this comment from people who haven't actually ever used them for more than a day and gleefully point to articles talking about stale docker images with vulnerabilities, ignoring that nearly the exact same problem happens with naive VMs + CM deployment methodologies. Or otherwise think they're magic, when they're not.
Not seeing anything to change my initial conclusion here.