Broken links, typos and suggestions

rontiv

In case a moderator replies to this post, please advise whether this kind of comments/remarks/findings should be posted as "Question" or "Discussion".

Regarding broken links:
a) On 05. Kubernetes Architecture > Kubernetes Architecture >> Networking Challenges
Broken link: "Weave"
https://www.weave.works/oss/net/
This was already reported in this forum in Link to "Weave" is broken on 05. Kubernetes Architecture, Networking Challenges

b) On 07. Minikube: Installing Local Kubernetes Clusters > Minikube: Installing Local Kubernetes Clusters >> Requirements for Running Minikube
Broken link: "VMwared Workstation"
https://www.vmware.com/in/products/workstation-pro/workstation-pro-evaluation.html

c) On 13. Kubernetes Volume Type > Kubernetes Volume Management >> Volume Types
broken link: "Microsoft Azure File Volume"
https://github.com/kubernetes/examples/tree/master/staging/volumes/azure_file
broken link: "NFS"
https://github.com/kubernetes/examples/tree/master/staging/volumes/nfs
broken link: "iSCSI"
https://github.com/kubernetes/examples/tree/master/volumes/iscsi

About typos and rewording suggestions:
d) On 04. Kubernetes > Kubernetes >> What is Kubernetes
Link: " License, Version 2.0" better as "Apache License, Version 2.0"

e) On 10. Authentication, Authorization, Admission Control > Authentication, Authorization, Admission Control >> Admission control
Typo last paragraph: "though custom plugins" I guess should be "through custom plugins"

f) On 12. Deploying a Standalone Application > Deploying a Standalone Application >> Exposing an Application (1)
At webserver-svc.yaml file the spec.selector.app should be "webserver"
I based my solution on the comment from harshan89 (Mar 22, 2024) on: at https://github.com/kubernetes/minikube/issues/17027

g) On 09. Kubernetes Building Blocks > Kubernetes Building Blocks >> Demo: Managing Node Applications with DaemonSets
At the beginning of the video after the cat operation (time 0:49s)
There's a last line "terminationGracePeriodSeconds: 30" on the manifest fluentd-agent.yaml that doesn't appear on the immediate related previous example on the content lesson; perhaps it should be added.

As bonuses:
h) I believe It hasn't been fix, the correction from this previous comment in this forum:
Create configmap from file or env-file

i) I remember getting stuck several times on the 3rd question of the knowledge check from lesson 03 "Container Orchestration" on a Windows system using Firefox. I didn't pay to much attention to the issue since it was solved using Edge or Chrome...

rontiv

Another suggestion for course content update: the "image" (to e.g. 'docker.io/library/busybox') on the "probe.yaml" manifest on 12. Deploying a Standalone Application > Deploying a Standalone Application >> Liveness Command
this was already mentioned twice in this forum on:
Any alternative to BusyBox? I get an error during the image pull for BusyBox
Wrong image registry for section '12 - Deploy a standalone application' (liveness command example)