Docker and Kubernetes
The Complete Guide

share ›
‹ links

Below are the top discussions from Reddit that mention this online Udemy course.

Build, test, and deploy Docker applications with Kubernetes while learning production-style development workflows

Reddemy may receive an affiliate commission if you enroll in a paid course after using these buttons to visit Udemy. Thank you for using these buttons to support Reddemy.

Taught by
Stephen Grider

Reddit Posts and Comments

0 posts • 22 mentions • top 20 shown below

r/docker • comment
2 points • ftinfo

I used this one and thought it was decent. If it’s not on sale right now, give it a few days and it will be.

r/webdev • comment
1 points • decimus5

I haven't used Vagrant much, but docker is worth learning. Then your local machines and the production server can be identical. Each developer can run the entire production stack on their laptop, make changes, and then easily merge those changes into the other code (Git), even if other people are currently editing the same files. This course is good, though I only watched the Docker parts.

r/AskReddit • comment
1 points • benethorpl

r/recruitinghell • comment
1 points • fluffycatsinabox

Yes, that's the class! Definitely a recommend- I find that the instructor handwaves over some of the details, which is a little frustrating but also very understandable given the breadth of services the course covers.

If you're interested, the Docker one I'm taking is here. Stephen Grider, the guy who teaches this and a bunch of other really good courses on Udemy, is an actual god. Instead of doing my program, I seriously should have just bought his courses and spent the rest of the money hiring someone to throw potatoes at me unless I self-studied.

Thank you again for the encouragement! Let's do great things.

r/node • comment
1 points • salttis

If you have time to spend on this you should check out this udemy course: Docker is just a container and doesnt scale on itself 🙂

r/webdev • comment
3 points • bleepbaboop

Just stay after it and persevere. A door will open. Consider all this interviewing thus far as practice. you are identifying weak areas as well as dialing in your value propositions and what you can bring to the table. I worked with a lady once who interviewed regularly to stay sharp. She was really casual about it.

As far as weaknesses, you mentioned Docker. Yes, you should have an understanding of containers and how they are used as part of the pipeline. This course was pretty thorough: I like Stephen Grider's teaching style. He goes the extra mile.

It's how we react in the face of adversity that determines our character. Stay confident and keep working hard.

r/docker • comment
1 points • midget1022

I was confused between this course and this one -

r/devops • comment
1 points • Some_ITguy

Have you looked at this course? Can't really say whether it's good or not, though.

r/cscareerquestions • comment
1 points • divulgingwords

This is the one, but definitely wait for it to be on sale for $10.

r/docker • comment
2 points • irungaia

Heres a sample Dockerized Flask app

And a service to the docker-compose file called 'mongo'. The host in you Mongo connection string in the Flask app with have to change from whatever it is now (probably localhost) to mongo for the Flask app in a container to connect to Mongo in a container.

I highly recommend this course. The first half is all Docker. It gets into Kubernetes in the second half.

r/WGUIT • comment
2 points • Most_Tangelo

>CKA with KodeKloud on Udemy

I may keep that in mind later down the line as I plan on skilling up with Docker and K8. My friend who works as a Solutions Architect for Apple actually recommended two from Udemy as well despite my own lack of finding a hit so far.\

r/docker • comment
2 points • xepo3abp

I have a very similar stack to yours and I'm following for deployment. Docker compose > Travis > EBS/ECS. He builds and deploys an app from ground 0 to production.

r/node • comment
1 points • godlikeplayer2

There is no blueprint for a microservice project and really depends on the size and scope of the project. You can start from a handful of simple node servers with express/koa that talk to each other via rest calls - basically like you do on the frontend. For example, a get request for a blog Article: gateway service (maybe with authenticating the user) -> article service -> comment service -> back to the user

Important is that every service should be stateless and at best be a 12 factor app.

for asynchronous stuff, you will need some kind of message broker like RabbitMq for example.

You could also use a federated Graphql schema, grpc or moleculer that have a bit different approach and are a pretty bleeding edge. Restful is still the mainstream way of doing inter-service communication but has some shortcomings that all these new paradigms try to solve.

Docker will be the minimum you need. Better at least docker-compose and for enterprise-grade environments, Kubernetes that handle most of the auto-scaling and service discovery stuff.

As the project grows, there will also more need in monitoring, tracing and error logging.

maybe you start from the beginning with some course. I went through this one a while ago. Covers a lot and uses nodejs

r/csharp • comment
1 points • OptimusPrime3600

Will definitely take a look. btw do you think these two courses are relevant to me?

r/kubernetes • comment
1 points • RelevantRope

>Udemy course by Stephen Grider

Is it this one?

r/cscareerquestions • comment
1 points • I_sell_pancakes

wait for this course to go on sale for like $10 or $15

r/docker • comment
1 points • lendarker

It depends on what you want to do. In general, I don't have a "central" nginx instance that maps stuff to the various projects. I have a docker-compose file per customer "setup" on my dev machine.

For example, to develop for customer A I need just an Apache with PHP 7.3, mariadb, then my docker-compose file would set up four docker containers:

  1. the webserver (apache container)
  2. the php container
  3. the mariadb container
  4. a phpmyadmin container, just because it's the easiest way to get quick access to the mariadb container

I'd map the webserver to port 80 on my local system, so http(s)://localhost goes to the website inside the container. I'd mal the phpmyadmin container to a different port, e.g. 8080 so I could also just call it up from the host.

I'd mount the web sources / html files to a directory on the host so that changes in development get immediately reflected in the webserver. The apache config gets either mounted at runtime or copied into the container during build (custom Dockerfile) so it knows to talk to the php container, etc.

Customer B might need an nginx reverse proxy, an nginx webserver to deliver static content, and an apache with mod-php to deliver dynamic content (say, because they require/want the use of htaccess files). The apache webserver also needs a database to fall back on.

In this case, I'd configure the reverse proxy container to map to port 80 on my local system, would use separate containers for the nginx, apache, mariadb containers. If you wanted to scale out the webservers horizontally, you could also add multiples of either of those, and for example put a haproxy load balancer in between the reverse proxy and the nginx webservers, and between the reverse proxy and the apache webservers, etc.

Using docker-compose makes it easy to define collections of containers to use together in a single YAML configuration file.

If your app requires a db cluster, or in most performance critical workloads, I would not use a dockerized db but connect to an existing db server/cluster.

Hope this helps a little.

Also, one of the rare times I actually found gold on Udemy, this docker course is very thorough:

r/docker • comment
1 points • Kernel_Internal

I'm typically not a huge fan of udemy but is actually pretty good and worth the sale price of $13.99 imo

r/developersIndia • comment
1 points • Sid_Stark

You can do a small scale version on your own.

Build a small app. Frontend, Backend, DB.

Dockerize it and deploy it. Maybe on Kubernetes.

Now you wanna do that automatically on change to any part. Use a jenkins script to auto update latest docker image and Argo CD to change the Kubernetes Image automatically. Congrats, now you have a CI/CD pipeline.

Load test your app now. Usually Jmeter to generate load, Prometheus and Grafana to monitor your Kubernetes cluster (CPU Usage, Request per minute etc) . See what's happening, Is you CPU usage through the roof or is your DB slow.

Now you can experiment with Kubernetes stuff - Horizontal Pod Autoscaling based on CPU/Memory requests. Try killing a pod and see what happens. Try downing a node. Stuff like that.

For Docker, I used Docker and Kubernetes Udemy Stephen Grider is an excellent teacher.

For Kubernetes, I would highly recommend this course - Kubernetes Hands On . I went from basically not knowing what Kubernetes is to deploying applications in Kubernetes within a week or two. It's that good. Highly recommend.

If you wanna learn more about how EKS (Managed Kubernetes on AWS) works AWS EKS Masterclass.

DevOps Huge Masterclass - If you want an all in one course. From Git -> Jenkins -> Docker -> Kubernetes -> Terraform -> Ansible.

Don't wanna pay for anything? TechWorld with Nana has some pretty good DevOps stuff.

After that it's all googling.

You (or probably) many of us are not going to be working at the scale that FAANG Engineering blogs mention. Just start small and you'll learn along the way.

InfoQ Youtube

Devoxx Youtube

These two channels have very interesting videos on the subject of System Design and Scaling. So keep an eye on them and connect the two.

It's very easy to get stuck in tutorial purgatory. So work on side projects and don't just follow the videos.

Hope this helps.

r/greece • comment
1 points • VDKay

Πολύ ωραίος! Ανάλογα πώς θες να συνεχίσεις θα πρότεινα:

  1. Για να συνεχίσεις πιο βαριά με Python, θα πρότεινα web development με Flask ( ή Django ( Αρχισε τα tutorials τους και στήσε serverάκι σπίτι σου, κάνε τα services να μιλάνε ματαξύ τους κλπ, και θα έχεις ήδη αποκτήσει εμπειρία για το 50% των θέσεων developer στην αγορά σήμερα.

  2. Μπορείς να δεις DevOps με Docker και Kubernetes. Προσωπικά ξεκίνησα αυτό ( το οποίο ξεκινάει από το 0 και είναι πολύ τίμιο και κατανοητό. Γενικά τα DevOps είναι πολύ trendy και game changers.

  3. Για πιο ακαδημαικά, μπορείς να τσεκάρεις τα Machine Learning services της Amazon ( ( Εχουν tutorials και παίζει να έχουν και free trial accounts.

Για τα 1 και 2 υπάρχει ήδη ΤΕΡΑΣΤΙΑ ζητηση στην Ελληνική αγορά, και λογικά θα αυξηθεί κι άλλο λόγω ιού πιστέυω (μιλάω με "φίλη" recruiter). Για το 3 είναι πολύ πιο παλούκι, αλλά αξίζει τον κόπο αν είσαι intellectual καυλωμένο άτομο και θα ήθελες να το δεις ακαδημαικά (master, phd σε οτιδήποτε έχει να κάνει με data analysis)