Welcome to the Linux Foundation Forum!
Typos
Typos
Slide 2.11 Kubernetes Users
Kubernetes is being adopted at a very rapid page.
Should be?
Kubernetes is being adopted at a very rapid pace.
Lab Three Page 3
$ docker run exec -ti k8s etcdctl ls /registry
Should be?
$ docker exec -ti k8s etcdctl ls /registry
..
0
Comments
In slide 6.6,
Should be
The extra space before pods will otherwise return an error rather than the getting the 2 resource types:
Thanks for the catch, you are correct. We will update the pages as fast as possible.
-sebastien
Thank you for letting us know. The corrections in the course will be made available once we release an updated version of the course.
Regards,
Flavia
This yml file refer to a namespace 258 instead of 248 ;-)
cat redis-lfs248.yaml
apiVersion: v1
kind: Pod
metadata:
namespace: lfs258
name: redis
spec:
containers:
- name: redis
image: redis
In the last block of the slide:
should be
"docker run exec -ti k8s etcdctl ls /registry" should be "docker exec -ti k8s etcdctl ls /registry" <-- Came here to say this. I got very frustrated trying to figure out why the command wasn't working. Took a break for a few days, came back with fresh eyes, and spotted "run" as the problem.
Thanks all for updating with other command errors/typos/errata. Next time I will check here first instead of banging my head against the wall.
should be
should be
Root cause should be when you made the pdf conversion ?
kubectl expose deployment/ghost --port=2368 —type=NodePort
instead of:
kubectl expose deployment/ghost --port=2368 --type=NodePort
For the line "(for a refresher on how to access the Course Resources, look at page 1.9)",
it should be "page 1.8" not "page 1.9"
For the line "(for a refresher on how to access the Course Resources, look at page 1.9)",
it should be "page 1.8" not "page 1.9"
should be
simple HHTP servers
outdated command ?
$ kubectl get rc --all-namespaces | grep dns
-no results
on kubernetes 1.5 and later I think is replica sets instead of replication controllers.
$ kubectl get rs --all-namespaces | grep dns
kube-system kube-dns-2431531914 1 1 1 1h
On slide 3.6.a the word "loose" is uwsed rather the intended word "lose"
Thanks for the course!
thank you all , all typos should have been corrected in the latest version of the course.
"Loose" has not been corrected yet.
Thank you, Christy, for letting us now. We will correct it in a future course update.
The default config is in ${HOME}/.kube/config (or ~/.kube/config or something like that ...) and not in $/.kube/config.
1.
shoud be
2.
I use OSX and have installed Homebrew. But when I run the command:
It shows:
Maybe the command can be ignored, and just run the command:
There is an effort to use Google's protobug serialization, but this remains experimental.
Not sure if intended, but might be a typo xD
Yes, a typo. It should be protobuf - as in protocol buffer.
Thanks!
On the $curl line there is a missing o in authorization in header.
The endpoint doesn't seem to need the auth though as it works fine misspelled or ommited.
Second sentance of the second paragraph"
"..., you will receive and error,"
-corrected to-
"..., you will receive an error."
Not one but at least two people went through things lookiing for typos and issues. Thank you all very much for letting us know what you have found. Early next week I will be using each of your notes to update the material.
Your efforts are very much appreciated!
Kind regards,
"Kubernetes clusters have to types of users service accounts and normal users,"
Should be
"Kubernetes clusters have 2 types of users 'service' accounts and 'normal users'."
Not sure if this is the right place to post this, but the "Picking the right Solution" link on page 3.11 is dead.
Thank you for letting us know. Unfortunately, a lot of URLs change overtime, especially when dealing with dynamic projects and rapidly changing documentation, and this is something we cannot control. The article mentioned, "Picking the right solution" can now be accessed here: https://v1-12.docs.kubernetes.io/docs/setup/pick-right-solution/. We will update the course in the next planned update .