Excellent course with a perfect hands on

good teachings but too basics

Great Course

good one

goood

nice

Overall, the course itself was nice. The course videos and labs helped solidify my experience with Docker, Kubernetes and OpenShift. However, the one thing that really killed this course was the final project. Other courses I've taken so far will tell you where to take screenshots, but this one did not. If that wasn't bad enough, you will need to delete something as instructed in the project guide and need to take screenshots of the state before the delete. I see in the discussion forums that a lot of people had to reset their projects due to not knowing about what screenshots to take until the very end. There are little to no threads discussing how to reset the final project.

I like that there are a some practical parts in this course, but I don't find helpful how they are represented (If I want to do everything on my own, I can't do it) . They already give you the code, with simple explanations. The course should have a homework part where you can create a dockerfile and .yml for yourself. Learn when to use each type of .yml . Also, Kubernetes has a dashboard, so it could be useful to learn how to use it too.

Good intentions to provide a controlled, simulated lab environment when the course matter consists of large systems. There was however quite some trouble with that lab environment. (Quick response and adjustments from the course responsibles though.) The theory was mostly an enumeration of facts about Docker, Kubernetes and OpenShift. I missed descriptions of problems and system design reasoning.

Week 2 was extremely difficult because every word I hear in the video is a new term and the tutorial didnt take time for the important ones to seep in. Hope that can be improved, perhaps by splitting the week's content more evenly. The remaining weeks and the labs were very nice and helpful.

the pear graded system (a student graded another student's work) is somehow not good. if one student didn't realize the grading standard well, or not understand the studying content so well, he would likely give wrong scores/comments to other's work.

Too much dense, terminology introduced without a real context, in particular in the module dedicated to OpenShift and Istio. Good the opportunity to try all the softwares directly in the browser.

I feel that the information provided was too breif and not explained in enough detail to adquately prepare the student to complete the test and assignments required for this course.

The topic is interesting and labs are good, but machine-recorded voice is of much lower value than a human trainer explaining concepts. I do prefer AWS tutors and training.

In this course you will hear tons of concepts in just a few minutes. It's up to you to search and understand those, if you want to be able to use them.

the slides are so monotone and full of text, and read by an AI voice, you hardly grasp the whole picture.

The content needs to be improved, there are a lot of new concepts and the explanations go way too fast.

Some problems in final exam, and instructions was not as clear as one gotten used to.

Too many problems with the Labs, but if fixed the course is smooth and nice

It was a bit confusing to understand and the lab environment was too slow.

lots of jargon, content explanation needs improvement

Too much guided assignments

Week 1 and Week 2 too long

Was a lot of rote-stating definition with little context as to what these different functionalities are used for with examples. Instead they only provide context for what they do within Docker and Kubernetes. This is quite confusing as this course is supposedly aimed at people with no experience of either application. Also the final project is a joke and is pretty much a step by step follow along guide with little room for actual learning or attempting to make the student think at all. Half the steps are incomplete in their description causing you to "click to view hint" to see what they are even asking, which just spits out the example code that you can just copy and paste to get the right answer. For example, "autoscale the deployment" and the only way to find out how much the assignment creator wants you to autoscale the deployment by is to view the hint. How that is supposed to test anything, I don't know.

Doesn't really seem to add anything you couldn't get from reading documentation. https://docs.docker.com/get-started/docker-overview/ https://kubernetes.io/docs/tutorials/kubernetes-basics/ https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/getting_started/openshift-overview