5 ms·

"It also gave me a duct tape feeling or batteries not included – like the critical pieces (docker support, DNS, load balancing) weren’t integrated into the orig

"It also gave me a duct tape feeling or batteries not included – like the critical pieces (docker support, DNS, load balancing) weren’t integrated into the original design." I'm sorry, this article^H^H^H^H^H rant isn't worth reading. I don't understand why people write these posts where they so poignantly display their complete ignorance alongside their strongly held opinions. It's tacky and doesn't reflect well. Load balancing is literally built-in via kube-proxy, NodePort and/or CloudProvider integration. Kube-DNS has existed for years (and is intentionally removable, but not at all duct-taped on). And the claim that Kubernetes didn't have Docker support... I mean, I literally don't even know what to say to that.

awinter-py 9y ago
my understanding is k8s was originally designed for lmctfy and docker was added shortly before launch
chepurko 9y ago
Yeah, lots of this article didn't make any sense. Especially with regards to Kubernetes. Most of this seems like reluctance of new Google or "Beta" technology. I tried my hand at Docker Compose, then Docker Swarm as "native" Docker solutions for quickly deploying scalable WordPress LEMP stacks. I would completely agree that neither of those are mature for this type of implementation, especially when it comes to persistent storage. Kubernetes, on the other hand, is another story. As long as you stick to using Docker strictly for building your container images, then Kube literally takes care of everything else. And this is all coming from a strictly ops perspective. EDIT: I would also note that Kubernetes docs are probably the best I've seen. They may be complicated, yes, so up your reading/comprehension skills and quit wining :)
user5994461 9y ago
These pieces were bolted on later, as an after thought. They are critical and should have been there for the start. 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 doesn't help that marketing around containers is "over promise and under deliver".
- chepurko 9y ago
  Yeah I would agree with that. I really dove into and started fully deploying Kube around v1.5. I would agree that Docker oversells and underperforms as well. I think it should be relegated strictly as a containerisation primitive and let the big boys handle orchestration. Docker documentation seems to lag behind a whole minor version of the actual software. It still baffles me how they are pushing Swarm as a production-ready orchestration tool but don't have persistent volumes completely figured out. But I'm just happy Kube is doing it right.
- colemickens 9y ago
  >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.
  - user5994461 9y ago
    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.

awinter-py 9y ago

my understanding is k8s was originally designed for lmctfy and docker was added shortly before launch

chepurko 9y ago

Yeah, lots of this article didn't make any sense. Especially with regards to Kubernetes. Most of this seems like reluctance of new Google or "Beta" technology. I tried my hand at Docker Compose, then Docker Swarm as "native" Docker solutions for quickly deploying scalable WordPress LEMP stacks. I would completely agree that neither of those are mature for this type of implementation, especially when it comes to persistent storage. Kubernetes, on the other hand, is another story. As long as you stick to using Docker strictly for building your container images, then Kube literally takes care of everything else. And this is all coming from a strictly ops perspective. EDIT: I would also note that Kubernetes docs are probably the best I've seen. They may be complicated, yes, so up your reading/comprehension skills and quit wining :)

user5994461 9y ago

These pieces were bolted on later, as an after thought. They are critical and should have been there for the start. 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 doesn't help that marketing around containers is "over promise and under deliver".

chepurko 9y ago
Yeah I would agree with that. I really dove into and started fully deploying Kube around v1.5. I would agree that Docker oversells and underperforms as well. I think it should be relegated strictly as a containerisation primitive and let the big boys handle orchestration. Docker documentation seems to lag behind a whole minor version of the actual software. It still baffles me how they are pushing Swarm as a production-ready orchestration tool but don't have persistent volumes completely figured out. But I'm just happy Kube is doing it right.
colemickens 9y ago
>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.
- user5994461 9y ago
  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.