This is a good one. Ideally I expect how Kubernetes works part to be for everyone except for few jargons like pods. And have an explanation for them.
May be I should have named it Kubernetes for anyone who knows Docker?
How about instead of calling something wrong, can you share the list of things that you feel needs an explanation. (feel free to comment) let us make this post for everyone :)
Well, you could start with explaining Kubernetes relies on Docker containers and how it's all related. I dug a little bit around Docker and Kubernetes seemed to appear here and there but I didn't have time to look it closer. So now I thought good maybe here I will know what's it all about. But here not a word about Kubernetes and Docker connection...
May be I should have named it Kubernetes for anyone who knows Docker?
Yes, that's probably it. I really don't know anything about Docker. But that's also a part of the problem: you mention Docker only after 85% of your article, and of course I didn't get to there.
can you share the list of things that you feel needs an explanation. (feel free to comment) let us make this post for everyone :)
I tried. But there's too much of it, and the article is really long. As I said above, the fact that you didn't even mention Docker for 5/6ths of your article is illustrative. Probably it would need a thorough rewrite, and it still wouldn't be worth it.
Hmm, I'm working with Docker and compose for a year or two but I have to admit i still don’t really understand the differences between pods, services, deployments and load balancing strategies.
For every section i thought, “oh this is interesting” and then the section was over and i did not really get it.
I think it’s hard to cover such a complex technology in an article but maybe you could have made up one example application that you’ve built with Kubernetes and explain the details along it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is a good one. Ideally I expect how Kubernetes works part to be for everyone except for few jargons like
pods. And have an explanation for them.May be I should have named it
Kubernetes for anyone who knows Docker?How about instead of calling something wrong, can you share the list of things that you feel needs an explanation. (feel free to comment) let us make this post for everyone :)
Well, you could start with explaining Kubernetes relies on Docker containers and how it's all related. I dug a little bit around Docker and Kubernetes seemed to appear here and there but I didn't have time to look it closer. So now I thought good maybe here I will know what's it all about. But here not a word about Kubernetes and Docker connection...
Yes, that's probably it. I really don't know anything about Docker. But that's also a part of the problem: you mention Docker only after 85% of your article, and of course I didn't get to there.
I tried. But there's too much of it, and the article is really long. As I said above, the fact that you didn't even mention Docker for 5/6ths of your article is illustrative. Probably it would need a thorough rewrite, and it still wouldn't be worth it.
Hmm, I'm working with Docker and compose for a year or two but I have to admit i still don’t really understand the differences between pods, services, deployments and load balancing strategies.
For every section i thought, “oh this is interesting” and then the section was over and i did not really get it.
I think it’s hard to cover such a complex technology in an article but maybe you could have made up one example application that you’ve built with Kubernetes and explain the details along it.