Kubernetes: Up and Running: Dive Into the Future of Infrastructure Paperback – 18 October 2019
|New from||Used from|
Frequently bought together
About the Author
From the Preface
Kubernetes: A Dedication
Kubernetes would like to thank every sysadmin who has woken up at 3 a.m. to restart a process. Every developer who pushed code to production only to find that it didn’t run like it did on their laptop. Every systems architect who mistakenly pointed a load test at the production service because of a leftover hostname that they hadn’t updated. It was the pain, the weird hours, and the weird errors that inspired the development of Kubernetes. In a single sentence: Kubernetes intends to radically simplify the task of building, deploying, and maintaining distributed systems. It has been inspired by decades of real-world experience building reliable systems and it has been designed from the ground up to make that experience if not euphoric, at least pleasant. We hope you enjoy the book!
Who Should Read This Book
Whether you are new to distributed systems or have been deploying cloud-native systems for years, containers and Kubernetes can help you achieve new levels of velocity, agility, reliability, and efficiency. This book describes the Kubernetes cluster orchestrator and how its tools and APIs can be used to improve the development, delivery, and maintenance of distributed applications.
Though no previous experience with Kubernetes is assumed, to make maximal use of the book you should be comfortable building and deploying server-based applications. Familiarity with concepts like load balancers and network storage will be useful, though not required. Likewise, experience with Linux, Linux containers, and Docker, though not essential, will help you make the most of this book.
No customer reviews
|5 star (0%)||0%|
|4 star (0%)||0%|
|3 star (0%)||0%|
|2 star (0%)||0%|
|1 star (0%)||0%|
Review this product
Most helpful customer reviews on Amazon.com
I recommend Kubernetes In Action instead.
While the author is the co-founder of the Kubernetes organization, he is not a great writer and is not the best at sharing this knowledge. The book lacks an overarching organization and offers little help to those who are not already somewhat familiar with Kubernetes.
So, what could've made the book better:
1. Add general explanations of how the various objects of Kubernetes work together. Explain Services, ReplicaSets, Deployments, ConfigMaps, etc. in terms of their hierarchy and how they work together from a very high level in the beginning. In fact, you can probably replace the whole Chapter 1 with this topic and it will be a lot more useful than writing about how Kubernetes works with hardware.
2. Write down EVERY command the reader has to run, and be more aware of the reader's environment. For example, at the beginning of the book we're asked to check our kubectl version, but the book doesn't say which version we need to be using. Turns out, some of the terms in the book are deprecated, e.g. "extensions/v1beta1" is replaced by "apps/v1". The book should've specified the version of kubectl the reader should install to have a good experience with the book. In another place, the book says if heapster does not exist in your kube-system, autoscaling will not work, but it doesn't say what to do to install heapster if it doesn't exist. In many other places, the book says "do this" and assumes you know the command. Very often, we don't.
3. Shrink the coverage on simpler concepts and expand on the complex ones. For example, DaemonSets are so similar to ReplicaSets. You might as well cover both in the same chapter and keep it short. Jobs, however, contains a more complex example and the chapter feels quite rushed. I understand you don't want to make a chapter too long, but what's stopping you from breaking a chapter into two?
Overall, I hope there'll be a third edition that covers the recently updated Kubernetes grammar, and with it these problems can be fixe.
Aside from being out of date, which is bound to happen with a fast-moving ecosystem, the authors seem to have the curse of knowledge, and their definitions of the core Kubernetes API objects are vague and provide little context.
I wish the book was updated as stuffs change in k8s world, I understand based on the published date the book was written with latest version then, though the concept is still valid but few commands I believe must be updated, not as a third edition but updates to this book, else I will have to invest in 3rd edt as well.