After years of ignoring it, I'm no longer able to fight the cloud urge. What's the best way to learn k8s in 2019?
For a very hands-on, getting-started tutorial, Katacoda is pretty awesome:
The Cult of Kubernetes
71–80 of 338 posts
Re: The Cult of Kubernetes
#72After years of ignoring it, I'm no longer able to fight the cloud urge. What's the best way to learn k8s in 2019?
With these these resources it will be difficult not to pass the CKA exam:
- kubernauts.slack.com & https://twitter.com/kubernauts/
- https://github.com/walidshaari/Kubernetes-Certified-Administ...
- https://docs.google.com/presentation/d/13EQKZSQDounPC1I6EC4P...
Re: The Cult of Kubernetes
#73I know the author has other goals (a desire to learn/practice kubernetes, and keep host their blog the same way as the other services they manage), but I'd like to point out here that if your end goal is a blog which auto-deploys on each push to master, Netlify has a fantastic free tier. I use Gatsby/Netlify, and operations/deployment is a 100% non-issue, and the site is very fast.
I'm aware of Netlify, my blog is not powered by a static site generator though. It's a Go app that flings out HTML, JSON-feed and RSS/Atom: https://github.com/Xe/site
Re: The Cult of Kubernetes
#74After years of ignoring it, I'm no longer able to fight the cloud urge. What's the best way to learn k8s in 2019?
Banging your head into things until it works, then figuring out why it worked.
Re: The Cult of Kubernetes
#75I think devs often make bad decision makers because in some sense tech is often an addiction rather than a pragmatic choice. The cycle of picking a tech, jumping ship to it, religiously evangelising it, riding the wave and then jumping ship to the next related tech is typical in my opinion. I try hard to correct for this bias but sometimes struggle with exactly the same thing. There's just something about wanting to…
> The cycle of picking a tech, jumping ship to it, religiously evangelising it, riding the wave and then jumping ship to the next related tech is typical in my opinion. To balance this with a counter example from the quieter group of people not "hot for the latest tech": I'm a "dev" and i've never had this problem, however I work for a small company, where everything I make and deploy I also have to maintain in some…
I’m curious which technologies you’ve ended up working with.
Re: The Cult of Kubernetes
#76After years of ignoring it, I'm no longer able to fight the cloud urge. What's the best way to learn k8s in 2019?
I'd recommend GitLab Auto-DevOps, although I'm sure there are others in this space, which provides a Heroku-like experience on Kubernetes. That way you don't have to learn Kubernetes in one big bang. You'll still probably need/want to learn Kubernetes eventually so you know what GitLab is doing for you and some of the tradeoffs involved but it's not a roadblock to getting stuff done, and starts you off with a fairly sane configuration.
Re: The Cult of Kubernetes
#77Earlier quoted context omitted.
I worked for someone who had mindset that whatever technology developers wanted was always good and ops should just shut up and put up with it because devs are the ones that make the money for the business. Very infuriating mindset to deal with.
And I've worked at companies where the devs where expected to know their place and not question ops, because ops was seen as the serious adults in the room keeping things running and devs where seen as easily distracted children chasing after the shiniest thing that most recently caught their attention. Made perfect sense when I was on the ops side and was super annoying when I was on the dev side :) Imagine if peopl…
Let's make a movement to bridge the fundamental divide between Dev and Ops.. we can call it OpsDev.
Re: The Cult of Kubernetes
#78Calling it a cult after growing up in one is a bit insulting. But, yes, I don't run much on my personal K8s clusters. But, I've lost count of how many problems Kubernetes has solved for folks I've worked with. It might not solve the simplicity use cases but, that's not the intended design of the tool to begin with.
- The group displays excessively zealous and unquestioning commitment to its leader
- Questioning, doubt and dissent are discouraged or even punished
- Mind-altering practices are used in excess to suppress doubts (corporate-speak counts)
- The group is elitist
- The group has a polarized us-versus-them mentality, which may cause conflict with the wider society
- The leader is not accountable to any authorities
- The group teaches or implies that the ends justify the means
- The leadership induces feelings of shame and/or guilt in order to influence and control members
- The group is preoccupied with bringing in new members
- The group is preoccupied with making money
- Members are expected to devote inordinate amounts of time to the group
- Members are encouraged or required to live and/or socialize only with other group members
- The most loyal members feel there can be no life outside the context of the group
Re: The Cult of Kubernetes
#79I am one of these guys who is using K8S at home. The reason is a unified platform for work and home environment.
What's the cheapest you can run a k8s cluster in the cloud? I've been looking to spin one up in AWS, but it looks remarkably expensive for running personal projects.
My cluster is at $30 a month, which is slightly more than my dokku server; but I get so much more out of it that I think it's worth it.
Re: The Cult of Kubernetes
#80After years of ignoring it, I'm no longer able to fight the cloud urge. What's the best way to learn k8s in 2019?
I did so in the beginning unf 2018 and after reading around and talking to some cloud people, I got the impression that the best idea is going right for serverless unless you have a real need for the stuff tha k8s gives you over it.