Shulou(Shulou.com)05/31 Report--

This article mainly explains "what are Kubernetes design patterns". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn what Kubernetes design patterns are.

There are many important concepts in Kubernetes, but understanding these design patterns is the most important:

Source: Kubernetes Design pattern

To help you understand, inspired by the GoF design pattern, the patterns are organized into the following categories.

Basic Mode-Foundational patterns

These patterns represent principles and best practices that containerized applications must follow in order to become good cloud native citizens. Regardless of the nature of your application, you should follow the following guidelines. Following these principles will help ensure that your application is suitable for automation on Kubernetes.

Probe inspection mode

Health detection requires that each container should implement a specific api to help the platform observe and manage applications in as healthy a way as possible. To achieve full automation, the local cloud application must be highly observable, allowing its status to be inferred so that Kubernetes can detect whether the application is started and ready to service the request. These observations affect the lifecycle management of Pods and when the application is made available to the public.

Declarative demand pattern

Declarable requirements explain why each container should declare its resource profile and limit it to specified resource requirements. The basis for successful application deployment, management, and coexistence in a shared cloud environment depends on identifying and declaring the application's resource requirements and runtime dependencies. This pattern describes how you should declare application requirements, whether they are run-time strong dependencies or resource requirements. Declaring your requirements is critical for Kubernetes to find the right place for your application in the cluster.

Automatic placement mode

Automatic placement explains how workload distribution in a multi-node cluster is affected. Placement is the core function of the Kubernetes scheduler, which is used to assign new pod to nodes that meet container resource requests and implement scheduling policies. This model describes the principle of Kubernetes scheduling algorithm and how to influence internal scheduling decisions from the outside.

Structured mode-Structural patterns

Having good cloud native containers is the first step, but not enough. The next step is to reuse containers and combine them into Pod to achieve the desired results. The patterns in this category focus on constructing and organizing containers in Pod to meet different use cases. These patterns are generated in order to affect the containers in Pod.

Initialize container design mode-Init Container

The Init container introduces a separate life cycle for initialization-related tasks and the main application container. The Init container provides a separate life cycle from the main application container through tasks related to initialization, and finally achieves the separation of concerns. This pattern introduces a basic Kubernetes concept that can be used whenever initialization logic is required.

Side car mode-Sidecar

Sidecar describes how to extend and enhance the functionality of an existing container without changing it. This pattern is a basic container pattern that allows single-purpose containers to work closely together.

Behavior pattern-Behavioral patterns

These patterns describe the management platform that ensures the lifecycle of Pods. Depending on the type of workload, Pod can run as a batch job until it is completed, or it can be scheduled to run on a regular basis. It can also run as a daemon service or as a singleton. Choosing the correct lifecycle management primitive will help you run Pod in the way you want.

Batch job mode

Batch Job describes how to run a separate atomic unit of work until it is complete. This mode is suitable for managing isolated atomic units of work in a distributed environment.

Stateful service mode

StatefulSet describes how to use Kubernetes to create and manage distributed stateful applications. Such applications require features such as persistent identity, network, storage, and ordinal. The StatefulSet primitive provides a strong guarantee for these builds and is ideal for managing stateful applications.

Service Discovery Model

Service discovery explains how clients access and discover instances that provide application services. To do this, Kubernetes provides a variety of mechanisms, depending on whether service consumers and producers are on or outside the cluster.

High-level Design pattern-Higher-leve

The patterns in this category are more complex and represent a higher level of application management patterns. Some of the patterns here, such as Controller, are timeless, and Kubernetes itself is built on them.

Controller mode

Controller is a mode that proactively monitors and maintains a set of Kubernetes resources in the desired state. The core of the Kubernetes itself consists of a series of controllers that periodically monitor and coordinate the current state of the application with the declared target state. This pattern describes how to use this core concept to extend the platform for our own applications.

Operator mode

Operator is a controller that uses CustomResourceDefinitions to encapsulate the operational knowledge of specific applications into specific structures and automation forms. The Operator mode allows us to extend the controller mode for greater flexibility and expressiveness. There are more and more Operator of Kubernetes, and this mode is becoming the main form of operating complex distributed systems.

Summary

Today, Kubernetes is the most popular container orchestration platform. It is jointly developed and supported by cutting-edge software companies and is provided as a service by all major cloud providers. Kubernetes supports Linux and Windows systems, as well as all major programming languages. The platform can also orchestrate and automate stateless and stateful applications, batch jobs, periodic tasks, and stateless service workloads. The pattern described here is the most commonly used of the broader patterns provided by Kubernetes, as shown below.

Kubernetes schemas are organized in different categories

Kubernetes is the application portability layer and the common infrastructure for every application on the cloud. If you are a software developer or architect, Kubernetes is likely to become a part of your life in one form or another. Learning the Kubernetes pattern described here will change the way you think about the platform. I believe that Kubernetes and the resulting concepts will be the basis of object-oriented programming concepts.

The pattern here is the GoF design pattern for container orchestration. Reading this article must not be the end, but the beginning of your Kubernetes journey.

Thank you for your reading, the above is the content of "what are the Kubernetes design patterns?" after the study of this article, I believe you have a deeper understanding of what Kubernetes design patterns have, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.