The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| PDF |
Page 19
Immediately after 1st paragraph |
Running the command 'kubectl -f create etcd-cluster-cr.yaml' doesn't seem to start up the cluster. Is there a step missing for k8s V1.20? I can see that the operator is running :
vagrant@k8s-master:~/op-book/chapters/ch03$ kubectl create -f etcd-cluster-cr.yaml
etcdcluster.etcd.database.coreos.com/example-etcd-cluster created
vagrant@k8s-master:~/op-book/chapters/ch03$ kubectl get pods
NAME READY STATUS RESTARTS AGE
etcd-operator-bf56bb648-gq2mp 1/1 Running 0 20m
hello-node-7567d9fdc9-5d977 1/1 Running 5 4d22h
vagrant@k8s-master:~/op-book/chapters/ch03$ kubectl get pods -A -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
default etcd-operator-bf56bb648-gq2mp 1/1 Running 0 25m 192.168.84.138 node-1 <none> <none>
default hello-node-7567d9fdc9-5d977 1/1 Running 5 4d22h 192.168.247.12 node-2 <none> <none>
kube-system calico-kube-controllers-69496d8b75-fz62s 1/1 Running 8 6d19h 192.168.235.223 k8s-master <none> <none>
kube-system calico-node-524tn 1/1 Running 15 6d19h 192.168.50.10 k8s-master <none> <none>
kube-system calico-node-jgg47 1/1 Running 12 6d18h 192.168.50.11 node-1 <none> <none>
kube-system calico-node-mxhtn 1/1 Running 12 6d18h 192.168.50.12 node-2 <none> <none>
kube-system coredns-74ff55c5b-5tgw9 1/1 Running 8 6d19h 192.168.235.225 k8s-master <none> <none>
kube-system coredns-74ff55c5b-bm9bw 1/1 Running 8 6d19h 192.168.235.224 k8s-master <none> <none>
kube-system etcd-k8s-master 1/1 Running 9 6d19h 192.168.50.10 k8s-master <none> <none>
kube-system kube-apiserver-k8s-master 1/1 Running 11 6d19h 192.168.50.10 k8s-master <none> <none>
kube-system kube-controller-manager-k8s-master 1/1 Running 12 6d19h 192.168.50.10 k8s-master <none> <none>
kube-system kube-proxy-ccjj6 1/1 Running 9 6d19h 192.168.50.10 k8s-master <none> <none>
kube-system kube-proxy-f2fgn 1/1 Running 8 6d18h 192.168.50.11 node-1 <none> <none>
kube-system kube-proxy-lp2j5 1/1 Running 9 6d18h 192.168.50.12 node-2 <none> <none>
kube-system kube-scheduler-k8s-master 1/1 Running 12 6d19h 192.168.50.10 k8s-master <none> <none>
kubernetes-dashboard dashboard-metrics-scraper-79c5968bdc-4b26w 1/1 Running 3 4d2h 192.168.84.137 node-1 <none> <none>
kubernetes-dashboard kubernetes-dashboard-5bf9fcbd4d-cbrn5 1/1 Running 3 4d2h 192.168.235.226 k8s-master <none> <none>
vagrant@k8s-master:~/op-book/chapters/ch03$ kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.4", GitCommit:"e87da0bd6e03ec3fea7933c4b5263d151aafd07c", GitTreeState:"clean", BuildDate:"2021-02-18T16:12:00Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.4", GitCommit:"e87da0bd6e03ec3fea7933c4b5263d151aafd07c", GitTreeState:"clean", BuildDate:"2021-02-18T16:03:00Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
vagrant@k8s-master:~/op-book/chapters/ch03$
|
Philip Boucherat |
Mar 22, 2021 |