This is curated? I look at "starting points" and still can't see the wood for the trees. And I'm far from a beginner since I've been doing the whole container thing for several years now.
Yes I think the mods should rename this to something more general like “List of kubernetes resources.” The awesome-* lists are not “curated” but rather a dumping ground of links one or two edges away from the core theme.
Curation in the context of Kubernetes is even more laughable because the community is a dumping ground of projects all trying to solve the same problems in slightly different ways. The CNCF Landscape is probably my favorite example of this. I don’t think they’ve ever seen a project they didn’t like.
Is there a way to learn kubernetes in a short time, or in a way that you can primarily use a GUI to interact with it?
Also why are there are so many distributions of it?
Udemy has good Kubernetes training. If you're hoping for an easy-to-use one-click GUI - good luck. vSphere 7 is finally integrating containers into their platform but even that is a mess to get up and running at this point.
There are so many distributions because it's COMPLICATED. Everyone is approaching it from a different angle trying to make it consumable by the enterprise.
Seconded. I used Rancher 1.x which used their own framework called Cattle. Since Kubernetes took off they moved exclusively to k8s. It's a great product.
https://infra.app/ is a great way to view, understand and troubleshoot apps on Kubernetes
The distros are provided by different vendors in the market (Red Hat, Pivotal, Rancher, others). It's a way for them to bundle in additional features while staying compliant with the standard Kubernetes APIs
Simple way to learn is to load up an AKS cluster (free for the master, simple to follow tutorials online), then learn to create a deployment and link a service to it (just a yaml file). It's really only an extra step or two on running a docker container.
ISTIO has been a good Kubernetes service mesh for a project I've been working on, and has been the hardest part to tie down though. So many obscure settings and hard-to-track-down information, especially in a sea of options and possible configurations.
Since our SSL is terminated in AWS our cluster was treating things as mostly "HTTP" internally and TLS-redirect HTTP->HTTPS wasn't working and other ISTIO redirects were returning HTTP when original context was HTTPS. It took lots of reading and digging through posts to find references to an "externalTrafficPolicy" setting that was crucial to fixing the problem. That was the most painful k8s/ISTIO thing that came up.
Kubernetes is a software varnish how a puppet master thinks how puppets should behave. Thing is, the puppets turn out to be almost humans and are a big heap of undeterministic behavior. But hey it is all in a sandbox so you can try and try again forever. It is like an avoid work machinery creating endless work and fun. It doesn't really matter... as an achievement.
22 comments
[ 2.7 ms ] story [ 59.0 ms ] threadCuration in the context of Kubernetes is even more laughable because the community is a dumping ground of projects all trying to solve the same problems in slightly different ways. The CNCF Landscape is probably my favorite example of this. I don’t think they’ve ever seen a project they didn’t like.
You can learn the basics in a week. It will take a very very long time to learn to be comfortable in it.
Kubernetes The Hard Way is the usual answer to "how do I learn this?"
It’s a great system in a lot of ways, but it sure has lots of quirks.
There are so many distributions because it's COMPLICATED. Everyone is approaching it from a different angle trying to make it consumable by the enterprise.
Rancher filled this role for me. Would recommend.
https://rancher.com/
https://github.com/rancher/rancher#rancher
The distros are provided by different vendors in the market (Red Hat, Pivotal, Rancher, others). It's a way for them to bundle in additional features while staying compliant with the standard Kubernetes APIs
[0]: https://github.com/derailed/k9s
https://www.youtube.com/playlist?list=PLcdHMZkfm5ujt60AwNh1E...
Also available in text but it’s not as detailed as the videos, basically my cheat sheets published:
https://avencera.com/learn
References:
https://chrisshort.net/kubernetes-illustrated-childrens-guid...
https://docs.google.com/spreadsheets/d/10NltoF_6y3mBwUzQ4bcQ... (The Kubernetes Learning Resources List)
https://github.com/jamiehannaford/what-happens-when-k8s
https://github.com/kubernetes/kubernetes
https://github.com/nkuba/k8s-admin-helper
https://github.com/ramitsurana/awesome-kubernetes
https://github.com/topics/cka?o=desc&s=stars
https://github.com/topics/kubernetes?o=desc&s=stars
https://k3s.io
https://kind.sigs.k8s.io
https://kubernauts-slack-join.herokuapp.com
https://kubernetes.io/docs/concepts
https://kubernetes.io/docs/reference/kubectl/cheatsheet
https://kubernetes.io/docs/tasks
https://kubernetes.io/docs/tasks/manage-kubernetes-objects/i...
https://kubernetes.io/training
https://kubernetesbyexample.com
https://labs.play-with-k8s.com
https://medium.com/faun/be-fast-with-kubectl-1-18-ckad-cka-3...
https://news.ycombinator.com/item?id=22597880 (Kind - run local Kubernetes clusters using Docker (k8s.io))
https://news.ycombinator.com/item?id=22689119 (Anyone have a recommended guide for Kubernetes?)
https://rancher.com
https://slack.k8s.io
https://techbeacon.com/enterprise-it/47-advanced-tutorials-m...
https://www.facebook.com/groups/...
Not to sound cocky, but there are probably below 1000 companies on earth that need it.
I prefer to stick to the Unix Canon myself.
Since our SSL is terminated in AWS our cluster was treating things as mostly "HTTP" internally and TLS-redirect HTTP->HTTPS wasn't working and other ISTIO redirects were returning HTTP when original context was HTTPS. It took lots of reading and digging through posts to find references to an "externalTrafficPolicy" setting that was crucial to fixing the problem. That was the most painful k8s/ISTIO thing that came up.
It really depends on your security posture. We wanted traffic between services within the service mesh to be encrypted too.