Cloud Native DevOps with Kubernetes

Errata for Cloud Native DevOps with Kubernetes, Second Edition

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Page not applicable in digital book
2nd paragraph Chapter 4

Chapter 4 second paragraph states - "Under the hood, the `kubectl run` command creates a Kubernetes resource called a Deployment"

Shouldn't this be "...creates a Kubernetes resource called a `Pod`"?

kubectl run --help
Create and run a particular image in a pod.

Note from the Author or Editor:
Thanks for catching this. You are correct that kubectl run now creates a Pod. In earlier versions it would create a Deployment. We updated the wording in a few other places in the book for this change, but this one got missed. Thanks again for submitting!

Arka  Jun 05, 2022 
Page 143
Image pull policy

On page 143, re Image pull policy it states a wrong but popular misunderstanding for the setting 'Always'. It does not always pull the image and lead to poor performance. It is similar to running ´docker pull’ which does not pull existing images (unless they have changed).

Here are the kubernetes doc on the subject:
« every time the kubelet launches a container, the kubelet queries the container image registry to resolve the name to an image digest. If the kubelet has a container image with that exact digest cached locally, the kubelet uses its cached image; otherwise, the kubelet pulls the image with the resolved digest, and uses that image to launch the container. »

Note from the Author or Editor:
Good catch, thanks for pointing this out!

Samuel Beaulieu  Aug 19, 2022 
Page 207-208

The section is called "Synk", and contains a few references to "Synk" but it should read "Snyk". The hyperlink is OK and goes to the right website. We had an argument at work on how to say snyk (sneak, snake, etc) and I still don't know :)

Note from the Author or Editor:
Thanks for catching this!

Samuel Beaulieu  Aug 20, 2022