kuberiter
Published in

kuberiter

Taj Mahal at Lego Land, Carlsbad CA — Lawrence Manickam

My book writing experience (The Kubernetes Ecosystem)

Few months back, I contemplated to write a book about DevOps with my friend Dr Pethuru Raj.

It was intriguing. Once I put my focus on it, several ideas popped up in my mind.

My Kuberiter team and other friends suggested the topic for the book and thanks to all of them. There were too many good suggestions that were interesting to see.

I had figured out that there are so many books for DevOps in the market. In fact, they are well thought out with clear narrative of any given DevOps pipeline. It is not wise to write another DevOps practice book in the overflowing market.

Why write about Kubernetes (K8S)?

Though there are several books and excellent blog content keep evolving for K8S, certain topics should still be addressed. Most of the K8S books talk about Architecture, Install, Configuration and best practices. However, Kubernetes is not a standalone product. It requires the support of Cloud functionalities and 10 other tools to function in order to utilize a DevOps pipeline. The massive orchestration nature of K8S requires a lot of ITIL discipline than before. The good news is that they are automated and there is no need to document them in an Office document.

Infrastructure as Code is the mantra. The deployment environment with relevant nonfunctional factors exists inside your GitHub repository. Those immutable objects can be recreated as many times as you want, destroy and recreate them.

The real challenge exists at the tools of DevOps toolchain.

A typical DevOps tool chain requires a code repository (GitHub), Build tool (Jenkins, Spinnaker), Container (Docker), Monitoring (Prometheus), Business Intelligence (Grafana), Logging (ELK), Scripting (ANSIBLE, Golang, Python), Service mesh (Istio), Labeling and Tracing (Zipkin), Automated deployments (Helm Chart) and other.

The configuration, positioning and operational state of each tool has a huge impact on your application deliverable at the K8S compute engine. Even failure of one tool and its dependencies affects your application release cycle and impacts team productivity.

I have witnessed the failure of Jenkins build tool that affected the creation of Docker images during a production rollout. The failure of Prometheus created a negative impression about the efficiency of DevOps pipeline at the eyes of stake holders.

Application release management is more complex than before. It’s a chaos. It is very hard to explain certain things to stake holders because the DevOps team doesn’t know the outcome of it until they will try it out.

This lead me to consider writing a book called

The Kubernetes Ecosystem

I did approach few publishers with Pethuru Raj. It’s a time-consuming process. It is tiresome to keep updating the book proposal, use their templates, setup meetings, back and forth emails and convincing them to get a common ground.

It became hard to explain and make them understand our vision. There could be a possibility to get a publisher if I am persistent but the hours that we spend on chasing a publisher is not profitable.

I have read few nice blogs online about how to self-publish a book. There are services such as blurb to print the material if necessary.

I decided to self-publish the book!

The below is the preliminary Table of Contents for the book and there will be more additions in the coming months.

Table of Contents

1. Introduction to Microservices, Containers and MultiCloud

1.1 Cloud Native Applications

1.2 Containers

1.3 Kubernetes

1.4 MultiCloud

1.5 Use case

2. Architecture

2.1 Kubernetes components

2.2 Kubernetes API Management

2.3 Kubernetes at AWS

2.4 Kubernetes at Azure

2.5 Kubernetes at GCP

2.6 Kubernetes at On-Premise

3. Kubernetes Install and Provisioning

3.1 Install and configuration at AWS

3.2 Install and configuration at Azure

3.3 Install and configuration at GCP

3.4 Install and configuration at VMware

3.5 Kubernetes at Windows OS

3.6 Kubernetes at Edge Devices

3.7 Code samples

3.8 Use case

4. Continuous Integration, Continuous Delivery and Continuous Deployment

4.1 Concepts of Continuous Integration and Continuous Delivery

4.2 Jenkins

4.3 Spinnaker

4.4 Build and package applications in a container

4.5 Code samples

4.6 Use case

5. Kubernetes Packaging and Deployments

5.1 Docker Registries

5.2 Helm Chart

5.3 Jenkins X

5.4 Kubernetes Deployments

5.5 Code samples

5.6 Use case

6. Kubernetes Networking and Storage

6.1 Kubernetes networking

6.2 Flannel networking

6.3 Weave net networking

6.4 GlusterFS volumes

6.5 Ceph volumes

6.6 Code samples

6.7 Use case

7. Kubernetes Service Mesh

7.1 Service mesh concepts

7.2 Conduit

7.3 Istio

7.4 Code samples

7.5 Use case

8. Kubernetes Security

8.1 Kubernetes security

8.2 Hashicorp Vault

8.3 Twistlock

8.4 Container security

8.5 Cloud security

8.6 Code samples

8.7 Use case

9. Kubernetes Logging and Monitoring

9.1 Kubernetes logging architecture

9.2 Fluentd logging

9.3 Splunk integration

9.4 Elasticsearch, Logstash and Kibana

9.5 Grafana Business Intelligence

9.6 Prometheus Architecture

9.7 Prometheus Monitoring

9.8 Code samples

9.9 Use case

10. Kubernetes testing and support tools

10.1 Kube monkey

10.2 Sonobuoy

10.3 Skopeo

10.4 OpenFaaS

10.5 Sidecar containers

10.6 Code samples

10.7 Use case

11. Kubernetes Service Providers

10.1 Kuberiter

10.2 Platform9

10.3 Rack Space

10.4 Red hat OpenShift

10.5 Stratoscale

10.6 Alibaba

10.7 AWS

10.8 MS Azure

10.9 GCP

11.0 Code samples

11.1 Use case

12. Kubernetes Artificial Intelligence and IoT

TBD

I can write a chapter or two per month and publish. The team of rock star developers at Kuberiter are committed to help us write the code and maintain the GitHub repository.

This effort needs authors and contributors.

If you are interested to write a chapter, please do contact me and we will discuss the details.

Thanks for reading this.

Lawrence Manickam is the Technical Founder of Kuberiter Inc, a Seattle based Start-up that provide JDK Services (Jenkins as a Service, Docker as a Service and Kubernetes as a Service) for MultiCloud.

Please subscribe at www.kuberiter.com to try our DevOps SaaS Services.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store