Book Image

Achieving Digital Transformation Using Hybrid Cloud

By : Vikas Grover, Ishu Verma, Praveen Rajagopalan
Book Image

Achieving Digital Transformation Using Hybrid Cloud

By: Vikas Grover, Ishu Verma, Praveen Rajagopalan

Overview of this book

Hybrid cloud technology can be leveraged by organizations aiming to build next-gen applications while safeguarding prior technological investments. This book will help you explore different hybrid cloud architectural patterns, whether designing new projects or migrating legacy applications to the cloud. You'll learn about the key building blocks of hybrid cloud enabling you to deploy, manage, and secure applications and data while porting the workloads between environments without rebuilding. Further, you’ll explore Kubernetes, GitOps, and Layer 3/7 services to reduce operational complexity. You'll also learn about nuances of security and compliance in hybrid cloud followed by the economics of hybrid cloud. You’ll gain a deep understanding of the concepts with use cases from telecom 5G and industrial manufacturing, giving you a glimpse into real industry problems resolved by hybrid cloud, and unlocking millions of dollars of opportunities for enterprises. By the end of this book, you'll be well-equipped to design and develop efficient hybrid cloud strategies, lead conversations with senior IT and business executives, and succeed in hybrid cloud implementation or transformation opportunities.
Table of Contents (12 chapters)
1
Part 1: Containers, Kubernetes, and DevOps for Hybrid Cloud
6
Part 2: Design Patterns, DevOps, and GitOps

Pod design patterns

Before we get into pod design patterns, I want to make sure that we all understand the nomenclature of Kubernetes.

Figure 4.1 – Node, namespace, pod, and service in Kubernetes

Figure 4.1 – Node, namespace, pod, and service in Kubernetes

As depicted in the diagram, we have nodes, namespaces, pods, and services:

  • Pod: This is the smallest and simplest unit of deployment in Kubernetes, which can contain one or more containers
  • Namespace: This is a way to create virtual clusters within a physical Kubernetes cluster to separate resources and provide access control and naming scope
  • Node: This is a physical or virtual machine that runs containerized applications and provides the computational resources for the Kubernetes cluster
  • Service: This is an abstraction layer that provides a stable IP address and DNS name for a set of pods and allows access to the pods from other parts of the cluster or from outside the cluster

Now, let’s look at design patterns.

Kubernetes...