5 ms·

Kubernetes must probably be one of the most tutorialized pieces of SW out there. You want a "crash course" on the platform of your choice? You got it. You want

Kubernetes must probably be one of the most tutorialized pieces of SW out there. You want a "crash course" on the platform of your choice? You got it. You want it for the price of your choice? You got it. The docs are great [1] and offer even interactive parts [2]. There are a ton of good materials on youtube. There are Coursera and EdX courses, e.g. [3] from Google and [4] from Red Hat. There are a ton of Udemy courses, e.g. [5]. I'm not even going to mention sites like Pluralsight (which now owns CloudGuru and CloudAcademy). I'm not even mentioning books on advanced Kubernetes and service mesh topics. I wonder what drives someone to write a 101-level tutorial on K8s. In my mind, there's such an overload of information on the topic that it must get lost among the greats. [1] https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/ https://kubernetes.io/docs/concepts/overview/what-is-kuberne... [2] https://kubernetes.io/docs/tutorials/kubernetes-basics/create-cluster/cluster-interactive/ https://kubernetes.io/docs/tutorials/kubernetes-basics/creat... [3] https://www.coursera.org/specializations/architecting-google-kubernetes-engine#courses https://www.coursera.org/specializations/architecting-google... [4] https://www.coursera.org/specializations/cloud-native-development-openshift-kubernetes https://www.coursera.org/specializations/cloud-native-develo... [5] https://www.udemy.com/course/learn-kubernetes/ https://www.udemy.com/course/learn-kubernetes/

rawoke083600 4y ago
To be fair. Just last night i was googling kubernetes and k3s tutorials. All of them on page 1 of SERPS are super simple and brilliant and ONLY show you how to add nodes to clusters. Ok now what ?? Ive drank the k-Koolaid signup for the newsletters but how do i get value from this 'thing' ??? When i code a webapp how do setup/config the db ? How do I do a regular LAMP app ? Lol i never thought i say this but i need a kubernetes tutorial on 'best practices' for common patterns. No for google scale but how do i kubernetify my run of the mil lamp app with 100kpage views a month ?? There seems to be a gap between the beginner and advance (kubernetes all things) levels ? Maybe that is the answer ?? The fact that the middle-situations(lamp apps with low-med traffic) tutorials dont exists means i dont need it ??
- ancieque 4y ago
  I would recommend Bret Fisher tutorials https://www.bretfisher.com/ https://www.bretfisher.com/
- vbezhenar 4y ago
  All you need exists on kubernetes.io. Start with https://kubernetes.io/docs/tutorials/hello-minikube/ https://kubernetes.io/docs/tutorials/hello-minikube/ and proceed. Read reference documentation on the same site whenever you need to dig somewhere. It's awesome. You don't need any other websites. I was able to build a kubernetes cluster and right now deploying multi-service application and I have had enough technical information on this website alone. As to answer your questions: You can start with DB as an ordinary container in a statefulset deployment. It's similar to docker. You configure it with environment variables. Advanced approach is operators, but you don't need those for simple start. Connection to DB is the same like docker. You use Kubernetes secrets instead of docker secrets and that's about it. My message assumes that you're proficient with docker. If you're not, I suggest to first learning docker. May be you don't need Kubernetes for your scale at all. And if you do, most docker concepts make sense in Kubernetes anyway.
  - rawoke083600 4y ago
    Cool thanks will have a look. Id be more interesting on where kubernetes (redundancy) fits into traditional redundancy ? Examples: 1. Do i still need gluster/ceph or do i use the longhorn thing ? 2. Db replication? Do i use the usual solutions of master-slaves and clusters or does multiple k-nodes take that over ? 3. Webserver LB with failover ? Do i use LB from hosting vendor, haproxy or does kubernetes have its own thing ?? From what I can tell as a kubernetes-noob the value is: 1) Reproducibility 2) Reliability via redundancy 3) AutoScaling. All of the abkve has to some degree a previous/current solution , so which do i give up/replace with kubernetes-tool ? Sorry yes Im a k-noob
    - timhaak 4y ago
      1 It depends. For larger scale gluster or ceph. But quiet a bit more work. Longhorn you can get up and working quickly. Though if you are on a cloud provider just use their storage system. 2 K8 doesn't magically solve replication unfortunately. Though there are helm charts that will automatically set up a replicated setup for you. I still need to solve backups. Once again if you are on a cloud provide. Just use their Db offering. 3 K8 doesn't have a default out of the box. The repo shows you how to setup traefik to handle this. On cloud providers they have normally integrated it with their lb already. For me the large advantages are reproducibility and no vendor lock in. Also give redundancy and quiet a bit of automation once set up. Auto scaling is always tricky. Lastly if you have the skills it can be far cheaper to run your own in metal. If you don't the the time most likely would be better spent actually coding. Depending where you are in the world and the relevant pay scales.
starkd 4y ago
This is no doubt a useful commment, since you provide other sources. However, it's not particularly a mark of courtesy to denigrate others' contribution to the space. If you had substantive criticism of the OP offered tutorial, it might be helpful. However, you offer none.
- BossingAround 4y ago
  I can see your point. Thanks for your comment, I'll try to restate my point next time.
brikis98 4y ago
Author here. I tried to answer your question in the first two paragraphs. But to add some context, given the nature of my work, I hear from developers on a nearly daily basis who are struggling to get started with the technologies mentioned in this blog post series, which include not only Kubernetes, but also Docker, AWS, and Terraform. In part, they are struggling because they are too scared to ask for help, and comments like yours only make that worse: you seem to be implying that the materials out there for Kubernetes are so good, that if you don't get it, there must be something wrong with you. And yet, there are thousands of devs who don't get it, so maybe for different people, there are different ways to learn? In discussions like this, I'm a fan of what Steve Yegge wrote about blogging [1]: > This is an important thing to keep in mind when you're blogging. Each person in your audience is on a different clock, and all of them are ahead of you in some ways and behind you in others. The point of blogging is that we all agree to share where we're at, and not poke fun at people who seem to be behind us, because they may know other things that we won't truly understand for years, if ever. That's why I write: to share what I know, from my particular perspective. Hopefully, that's useful to some people out there. If it's not useful to you, no problem! And for the record, I agree the Kubernetes docs are great, including those interactive tutorials: if you read the series, you'd see I actually recommend those exact docs at the end of the post [2]. [1] https://sites.google.com/site/steveyegge2/you-should-write-blogs https://sites.google.com/site/steveyegge2/you-should-write-b... [2] https://blog.gruntwork.io/a-crash-course-on-kubernetes-a96c3891ad82#8240 https://blog.gruntwork.io/a-crash-course-on-kubernetes-a96c3...
waynesonfire 4y ago
I just don't want to do that, no thanks. I've spent so much time learning about how an OS can solve these problems and these lessons have paid dividends many times over my career. Instead, I will continue to invest in the core foundation. I'm not interested in re-learning these abstractions reading [1]-[5] tutorials plus many more and studying an unrefined, new layer of complicated abstractions built on top of the OS--the OS is difficult enough. I'll only _use_ k8s when it's managed and supported by a team of 10+ engineers, which is what it requires. Plus, it's not just k8s; you have concourse, spinnaker, artifactory, some sort of cluster templating, kops? to template your k8s deployments across DCs and environments, (I don't know what the community uses, we built our own in-house tool). It's all so gross. My rejection of these systems has lead me to invest in FreeBSD. There was a learning curve and I'm certainly not as fluent in this system as I am with Linux but I'm in a place where I'm in control of the OS and have at my disposal solid, refined tools to help me masterfully construct the infrastructure to solve my problems. And, every time I solve a problem in this space my foundational understanding grows and these lessons will pay dividends into the future, or so I hope. I'm utilizing FreeBSD because docker / k8s and I'll add systemd to the list, are missing and thus the community solves problems in a different way that better aligns with my values. FreeBSD isn't easier, I've been stumped on problems countless numbers of times but when I find a solution, it scales. What I mean by that is I have a better understanding of a system that can solve a larger class of problems than if I was in the docker / k8s ecosystem. YMMV.
- BossingAround 4y ago
  That sounds like a bit of an extreme reaction to what seems to be a "this technology is yucky and I don't like it" problem.
  - waynesonfire 4y ago
    No, you're way off. Maybe my reaction is extreme, but my problem isn't. What's yucky is that you're trying to convince people that reading five tutorials on k8s will make them productive. No, the problem, and I'll repeat it since you conveniently skipped over it, k8s requires 10+ engineers to maintain and manage, full time. _I_ don't have 10 engineers and thus it's the wrong tool for me and I've decided to not invest in it.
TuringNYC 4y ago
>> I wonder what drives someone to write a 101-level tutorial on K8s. When I was going thru k8s tutorials several years ago, one issue was how quickly the tutorials became outdated with changes in k8s. Then you'd spend only half your effort on the the tutorial, and the other half debugging why the tutorial wasnt working.
throwaway894345 4y ago
Sadly last I checked there were relatively few tutorials for setting up on bare metal (or rather, they neglect important topics like setting up net worked volumes or other things that are very likely to be required by an application.

rawoke083600 4y ago

To be fair. Just last night i was googling kubernetes and k3s tutorials. All of them on page 1 of SERPS are super simple and brilliant and ONLY show you how to add nodes to clusters. Ok now what ?? Ive drank the k-Koolaid signup for the newsletters but how do i get value from this 'thing' ??? When i code a webapp how do setup/config the db ? How do I do a regular LAMP app ? Lol i never thought i say this but i need a kubernetes tutorial on 'best practices' for common patterns. No for google scale but how do i kubernetify my run of the mil lamp app with 100kpage views a month ?? There seems to be a gap between the beginner and advance (kubernetes all things) levels ? Maybe that is the answer ?? The fact that the middle-situations(lamp apps with low-med traffic) tutorials dont exists means i dont need it ??

ancieque 4y ago
I would recommend Bret Fisher tutorials https://www.bretfisher.com/ https://www.bretfisher.com/
vbezhenar 4y ago
All you need exists on kubernetes.io. Start with https://kubernetes.io/docs/tutorials/hello-minikube/ https://kubernetes.io/docs/tutorials/hello-minikube/ and proceed. Read reference documentation on the same site whenever you need to dig somewhere. It's awesome. You don't need any other websites. I was able to build a kubernetes cluster and right now deploying multi-service application and I have had enough technical information on this website alone. As to answer your questions: You can start with DB as an ordinary container in a statefulset deployment. It's similar to docker. You configure it with environment variables. Advanced approach is operators, but you don't need those for simple start. Connection to DB is the same like docker. You use Kubernetes secrets instead of docker secrets and that's about it. My message assumes that you're proficient with docker. If you're not, I suggest to first learning docker. May be you don't need Kubernetes for your scale at all. And if you do, most docker concepts make sense in Kubernetes anyway.
- rawoke083600 4y ago
  Cool thanks will have a look. Id be more interesting on where kubernetes (redundancy) fits into traditional redundancy ? Examples: 1. Do i still need gluster/ceph or do i use the longhorn thing ? 2. Db replication? Do i use the usual solutions of master-slaves and clusters or does multiple k-nodes take that over ? 3. Webserver LB with failover ? Do i use LB from hosting vendor, haproxy or does kubernetes have its own thing ?? From what I can tell as a kubernetes-noob the value is: 1) Reproducibility 2) Reliability via redundancy 3) AutoScaling. All of the abkve has to some degree a previous/current solution , so which do i give up/replace with kubernetes-tool ? Sorry yes Im a k-noob
  - timhaak 4y ago
    1 It depends. For larger scale gluster or ceph. But quiet a bit more work. Longhorn you can get up and working quickly. Though if you are on a cloud provider just use their storage system. 2 K8 doesn't magically solve replication unfortunately. Though there are helm charts that will automatically set up a replicated setup for you. I still need to solve backups. Once again if you are on a cloud provide. Just use their Db offering. 3 K8 doesn't have a default out of the box. The repo shows you how to setup traefik to handle this. On cloud providers they have normally integrated it with their lb already. For me the large advantages are reproducibility and no vendor lock in. Also give redundancy and quiet a bit of automation once set up. Auto scaling is always tricky. Lastly if you have the skills it can be far cheaper to run your own in metal. If you don't the the time most likely would be better spent actually coding. Depending where you are in the world and the relevant pay scales.

starkd 4y ago

This is no doubt a useful commment, since you provide other sources. However, it's not particularly a mark of courtesy to denigrate others' contribution to the space. If you had substantive criticism of the OP offered tutorial, it might be helpful. However, you offer none.

BossingAround 4y ago
I can see your point. Thanks for your comment, I'll try to restate my point next time.

brikis98 4y ago

Author here. I tried to answer your question in the first two paragraphs. But to add some context, given the nature of my work, I hear from developers on a nearly daily basis who are struggling to get started with the technologies mentioned in this blog post series, which include not only Kubernetes, but also Docker, AWS, and Terraform. In part, they are struggling because they are too scared to ask for help, and comments like yours only make that worse: you seem to be implying that the materials out there for Kubernetes are so good, that if you don't get it, there must be something wrong with you. And yet, there are thousands of devs who don't get it, so maybe for different people, there are different ways to learn? In discussions like this, I'm a fan of what Steve Yegge wrote about blogging [1]: > This is an important thing to keep in mind when you're blogging. Each person in your audience is on a different clock, and all of them are ahead of you in some ways and behind you in others. The point of blogging is that we all agree to share where we're at, and not poke fun at people who seem to be behind us, because they may know other things that we won't truly understand for years, if ever. That's why I write: to share what I know, from my particular perspective. Hopefully, that's useful to some people out there. If it's not useful to you, no problem! And for the record, I agree the Kubernetes docs are great, including those interactive tutorials: if you read the series, you'd see I actually recommend those exact docs at the end of the post [2]. [1] https://sites.google.com/site/steveyegge2/you-should-write-blogs https://sites.google.com/site/steveyegge2/you-should-write-b... [2] https://blog.gruntwork.io/a-crash-course-on-kubernetes-a96c3891ad82#8240 https://blog.gruntwork.io/a-crash-course-on-kubernetes-a96c3...

waynesonfire 4y ago

I just don't want to do that, no thanks. I've spent so much time learning about how an OS can solve these problems and these lessons have paid dividends many times over my career. Instead, I will continue to invest in the core foundation. I'm not interested in re-learning these abstractions reading [1]-[5] tutorials plus many more and studying an unrefined, new layer of complicated abstractions built on top of the OS--the OS is difficult enough. I'll only _use_ k8s when it's managed and supported by a team of 10+ engineers, which is what it requires. Plus, it's not just k8s; you have concourse, spinnaker, artifactory, some sort of cluster templating, kops? to template your k8s deployments across DCs and environments, (I don't know what the community uses, we built our own in-house tool). It's all so gross. My rejection of these systems has lead me to invest in FreeBSD. There was a learning curve and I'm certainly not as fluent in this system as I am with Linux but I'm in a place where I'm in control of the OS and have at my disposal solid, refined tools to help me masterfully construct the infrastructure to solve my problems. And, every time I solve a problem in this space my foundational understanding grows and these lessons will pay dividends into the future, or so I hope. I'm utilizing FreeBSD because docker / k8s and I'll add systemd to the list, are missing and thus the community solves problems in a different way that better aligns with my values. FreeBSD isn't easier, I've been stumped on problems countless numbers of times but when I find a solution, it scales. What I mean by that is I have a better understanding of a system that can solve a larger class of problems than if I was in the docker / k8s ecosystem. YMMV.

BossingAround 4y ago
That sounds like a bit of an extreme reaction to what seems to be a "this technology is yucky and I don't like it" problem.
- waynesonfire 4y ago
  No, you're way off. Maybe my reaction is extreme, but my problem isn't. What's yucky is that you're trying to convince people that reading five tutorials on k8s will make them productive. No, the problem, and I'll repeat it since you conveniently skipped over it, k8s requires 10+ engineers to maintain and manage, full time. _I_ don't have 10 engineers and thus it's the wrong tool for me and I've decided to not invest in it.

TuringNYC 4y ago

>> I wonder what drives someone to write a 101-level tutorial on K8s. When I was going thru k8s tutorials several years ago, one issue was how quickly the tutorials became outdated with changes in k8s. Then you'd spend only half your effort on the the tutorial, and the other half debugging why the tutorial wasnt working.

throwaway894345 4y ago

Sadly last I checked there were relatively few tutorials for setting up on bare metal (or rather, they neglect important topics like setting up net worked volumes or other things that are very likely to be required by an application.