What do you think?
Rate this book
DevOps with Kubernetes: Accelerating software delivery with container orchestrators
Key FeaturesLearning DevOps, container, and Kubernetes within one book.Leverage Kubernetes as a platform to deploy, scale, and run containers efficiently.A practical guide towards container management and orchestrationBook DescriptionContainerization is said to be the best way to implement DevOps. Google developed Kubernetes, which orchestrates containers efficiently and is considered the frontrunner in container orchestration. Kubernetes is an orchestrator that creates and manages your containers on clusters of servers. This book will guide you from simply deploying a container to administrate a Kubernetes cluster, and then you will learn how to do monitoring, logging, and continuous deployment in DevOps. The initial stages of the book will introduce the fundamental DevOps and the concept of containers. It will move on to how to containerize applications and deploy them into. The book will then introduce networks in Kubernetes. We then move on to advanced DevOps skills such as monitoring, logging, and continuous deployment in Kubernetes. It will proceed to introduce permission control for Kubernetes resources via attribute-based access control and role-based access control. The final stage of the book will cover deploying and managing your container clusters on the popular public cloud Amazon Web Services and Google Cloud Platform. At the end of the book, other orchestration frameworks, such as Docker Swarm mode, Amazon ECS, and Apache Mesos will be discussed.
What you will learnLearn fundamental and advanced DevOps skills and toolsGet a comprehensive understanding for containerLearn how to move your application to container worldLearn how to manipulate your application by KubernetesLearn how to work with Kubernetes in popular public cloudImprove time to market with Kubernetes and Continuous DeliveryLearn how to monitor, log, and troubleshoot your application with KubernetesAbout the AuthorHideto Saito has around 20 years of experience in the computer industry. In 1998, while working for Sun Microsystems Japan, he was impressed with Solaris OS, OPENSTEP, and Sun Ultra Enterprise 10000 (AKA StarFire). Then, he decided to pursue the UNIX and MacOS X operating systems.
In 2006, he relocated to Southern California as a software engineer to develop products and services running on Linux and MacOS X. He was especially renowned for his quick Objective-C code when he was drunk.
He is also an enthusiast of Japanese anime, drama, and motorsports, and loves Japanese Otaku culture.
Hui-Chuan Chloe Lee is a DevOps and software developer. She has worked in the software industry on a wide range of projects for over 5 years. As a technology enthusiast, Chloe loves trying and learning new technologies, which makes her life happier and more fulfilled. In her free time, she enjoys reading, traveling, and spending time with the people she loves.
Cheng-Yang Wu has been tackling with infrastructure and system reliability since he received his master's degree in Computer Science from National Taiwan University. His laziness prompted him to master DevOps skills to maximize his efficiency at work so as to squeeze in writing codes for fun. He enjoys cooking as it's just like working with software -- a perfect dish always comes from balanced flavors and fine-tuned tastes.
Table of ContentsWhat is DevOpsDevOps with ContainerGetting started with KubernetesWorki
What you will learnLearn fundamental and advanced DevOps skills and toolsGet a comprehensive understanding for containerLearn how to move your application to container worldLearn how to manipulate your application by KubernetesLearn how to work with Kubernetes in popular public cloudImprove time to market with Kubernetes and Continuous DeliveryLearn how to monitor, log, and troubleshoot your application with KubernetesAbout the AuthorHideto Saito has around 20 years of experience in the computer industry. In 1998, while working for Sun Microsystems Japan, he was impressed with Solaris OS, OPENSTEP, and Sun Ultra Enterprise 10000 (AKA StarFire). Then, he decided to pursue the UNIX and MacOS X operating systems.
In 2006, he relocated to Southern California as a software engineer to develop products and services running on Linux and MacOS X. He was especially renowned for his quick Objective-C code when he was drunk.
He is also an enthusiast of Japanese anime, drama, and motorsports, and loves Japanese Otaku culture.
Hui-Chuan Chloe Lee is a DevOps and software developer. She has worked in the software industry on a wide range of projects for over 5 years. As a technology enthusiast, Chloe loves trying and learning new technologies, which makes her life happier and more fulfilled. In her free time, she enjoys reading, traveling, and spending time with the people she loves.
Cheng-Yang Wu has been tackling with infrastructure and system reliability since he received his master's degree in Computer Science from National Taiwan University. His laziness prompted him to master DevOps skills to maximize his efficiency at work so as to squeeze in writing codes for fun. He enjoys cooking as it's just like working with software -- a perfect dish always comes from balanced flavors and fine-tuned tastes.
Table of ContentsWhat is DevOpsDevOps with ContainerGetting started with KubernetesWorki
726 pages, Kindle Edition
Published October 16, 2017
33 people are currently reading
57 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 7 of 7 reviews
July 10, 2018
This book is a real mixed bag. 3 people wrote different chapters and then they were assembled together. There's no consistent voice or style. It needs some serious editing.
A lot of the template samples throughout the ebook were incorrect due to formatting errors. YAML is whitespace sensitive. Corresponding templates in the github repos (yes, there are two. One under the publisher's account and another specific to the book with a little extra content) that I checked were correct. The use of pre tags caused a lot of the commands to ran off the side of the page.
Three chapters ("Working with storage", "Kubernetes on AWS/GCP") used screenshots of terminals to display templates and command output. This really broke the flow.
The book starts off really poorly. The opening chapter on the evolution of software development is the worst I've ever read. It's disjointed, inaccurate and does not flow. It also describes "Devops" as a silo which is the opposite of the movement's original intention.
The "DevOps with Container" chapter was a bit odd. A quick rundown of Docker. Surely someone looking at Kubernetes already knows of containers? Or would benefit from reading a proper treatment of the topic if they don't (up sell!) And why bother with mentioning docker-compose and giving examples? I thought this was a Kubernetes book.
"Getting started with Kubernetes" chapter gives step by step instruction on installing minikube on MacOS. Forget the Windows and linux guys, they can figure it out themselves. They then move on to using kubectl, forgetting to mention that it needs installing first.
There's a whole chapter called "Continuous Delivery" which then describes Continuous Deployment. There is a difference, and it does matter. This was a reoccurring issue through the book.
The four properly technical sections about Kubernetes, "Network and Security" through to "Cluster Administration" were really well written. They're sorely let down by the opening chapters and bad editing.
A lot of the template samples throughout the ebook were incorrect due to formatting errors. YAML is whitespace sensitive. Corresponding templates in the github repos (yes, there are two. One under the publisher's account and another specific to the book with a little extra content) that I checked were correct. The use of pre tags caused a lot of the commands to ran off the side of the page.
Three chapters ("Working with storage", "Kubernetes on AWS/GCP") used screenshots of terminals to display templates and command output. This really broke the flow.
The book starts off really poorly. The opening chapter on the evolution of software development is the worst I've ever read. It's disjointed, inaccurate and does not flow. It also describes "Devops" as a silo which is the opposite of the movement's original intention.
The "DevOps with Container" chapter was a bit odd. A quick rundown of Docker. Surely someone looking at Kubernetes already knows of containers? Or would benefit from reading a proper treatment of the topic if they don't (up sell!) And why bother with mentioning docker-compose and giving examples? I thought this was a Kubernetes book.
"Getting started with Kubernetes" chapter gives step by step instruction on installing minikube on MacOS. Forget the Windows and linux guys, they can figure it out themselves. They then move on to using kubectl, forgetting to mention that it needs installing first.
There's a whole chapter called "Continuous Delivery" which then describes Continuous Deployment. There is a difference, and it does matter. This was a reoccurring issue through the book.
The four properly technical sections about Kubernetes, "Network and Security" through to "Cluster Administration" were really well written. They're sorely let down by the opening chapters and bad editing.
October 30, 2022
DevOps and Kubernetes are prevalent topics nowadays.
This 2017 book by Packt Publishing wants to explain DevOps using containerised platforms, especially Kubernetes.
The first chapter is a very quick tour of the foundation of the DevOps methodology: micro-services, continuous delivery, and infrastructure as a code...
The second chapter describes what the containers are and how to use Docker, the dockerfiles and the docker-compose command.
The central part of the book is on Kubernetes, its resources, how to deploy and monitor our applications on Kubernetes, and how we configure and manage a Kubernetes cluster.
The final chapters are on AWS and Google Cloud offerings and how to implement a Kubernetes cluster on them.
The book could have been a good overview of the DevOps approach using Kubernetes but it is affected by one negative aspect: the book's English is not good, there are several grammar errors and the reading is sometimes not easy. This is somehow surprising for a UK-based publisher.
Important: there is a second edition of the book, published in 2019 (ISBN 1789533996). I expect the new edition will also cover some more recent DevOps concepts like, for example, the GitOps approach.
This 2017 book by Packt Publishing wants to explain DevOps using containerised platforms, especially Kubernetes.
The first chapter is a very quick tour of the foundation of the DevOps methodology: micro-services, continuous delivery, and infrastructure as a code...
The second chapter describes what the containers are and how to use Docker, the dockerfiles and the docker-compose command.
The central part of the book is on Kubernetes, its resources, how to deploy and monitor our applications on Kubernetes, and how we configure and manage a Kubernetes cluster.
The final chapters are on AWS and Google Cloud offerings and how to implement a Kubernetes cluster on them.
The book could have been a good overview of the DevOps approach using Kubernetes but it is affected by one negative aspect: the book's English is not good, there are several grammar errors and the reading is sometimes not easy. This is somehow surprising for a UK-based publisher.
Important: there is a second edition of the book, published in 2019 (ISBN 1789533996). I expect the new edition will also cover some more recent DevOps concepts like, for example, the GitOps approach.
April 24, 2022
The authors seem to know their material, and it's presented in a good order. Unfortunately, none of them are fluent in written English, and it shows. It's not too bad when they're giving an overview of the history of software development to show how we got to where we are now. It's worse when they're deep in the technical stuff: it's hard enough to follow the material without having to wrestle with the language.
Here's the paragraph that made me give up. It's in a section describing how, when it's short of either CPU or memory, Kubernetes kills BestEffort pods (sets of containers) first, then Burstable ones, then Guaranteed ones:
This book desperately needs the help of someone fluent in written English, and I think less of Packt for not working with the authors on this. If this is fixed in the next edition, I'll be happy to give a higher rating.
Here's the paragraph that made me give up. It's in a section describing how, when it's short of either CPU or memory, Kubernetes kills BestEffort pods (sets of containers) first, then Burstable ones, then Guaranteed ones:
Even though, change to configure resource limit only, but if container A has CPU limit only, then container B has memory limit only, then result will also be Burstable again because Kubernetes knows only either limit
This book desperately needs the help of someone fluent in written English, and I think less of Packt for not working with the authors on this. If this is fixed in the next edition, I'll be happy to give a higher rating.
April 18, 2019
One hates to criticize non-native speakers for their lack of facility but then one hates even more to struggle with technical books that are incomprehensible in parts.
It's not that there's not good information here. I think there is. But simple things like not using articles (a, an, the) makes distinguishing generalities from specifics very challenging. Consider a word like "service" and the difference between "a service", "the service" and "service" as a verb, and you get some idea of how laborious this was to read.
If you know what's going on, of course, the distinctions are probably obvious—but if you know what's going on, why are you reading this? Now, that's not entirely fair, of course: You could have a rough idea about the processes and be able to pick through this. I know what little knowledge I had was crucial to getting what I could get out of it.
Not sure what Packt was thinking. My first DNF.
It's not that there's not good information here. I think there is. But simple things like not using articles (a, an, the) makes distinguishing generalities from specifics very challenging. Consider a word like "service" and the difference between "a service", "the service" and "service" as a verb, and you get some idea of how laborious this was to read.
If you know what's going on, of course, the distinctions are probably obvious—but if you know what's going on, why are you reading this? Now, that's not entirely fair, of course: You could have a rough idea about the processes and be able to pick through this. I know what little knowledge I had was crucial to getting what I could get out of it.
Not sure what Packt was thinking. My first DNF.
February 5, 2018
Interesting book with real hands-on examples. I found this book very useful and well structured. A good illustration of the different components of kubernetes and containers in general.
June 12, 2018
An essential book for k8s devops!
February 13, 2024
The book assumes some implicit assumptions or prerequisites. Its language could be more precise or clear & presentation more explicit then it will be more informative & economical
Displaying 1 - 7 of 7 reviews