Deployment - Strategy

 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

There are several deployment strategies in Kubernetes, including:

Rolling updates: This is the default deployment strategy in Kubernetes. Rolling updates replace the old version of an application with a new version in a controlled and gradual manner, ensuring that the application remains available during the update process.


Blue/Green deployment: This strategy involves running two identical environments (blue and green) simultaneously, but only one environment is serving traffic at any given time. The new version of the application is deployed in the inactive environment (green), tested, and verified before traffic is redirected to it.


Canary deployment: This strategy is similar to the Blue/Green deployment, but it is more targeted. Only a small percentage of users (canary users) are directed to the new version of the application, allowing for early testing and feedback before rolling out the update to all users.


A/B testing: This strategy involves running two different versions of an application simultaneously, and directing a portion of traffic to each version. This enables the evaluation of different versions to determine which performs better.


Shadow deployment: This strategy involves deploying the new version of the application alongside the old version, but not routing any traffic to it. Instead, the new version captures traffic data from the production environment to evaluate performance and stability.

Recreate deployment: This strategy involves deleting the existing version of an application before deploying the new version. This approach ensures that there is no overlap between the old and new versions of the application, but it can also result in downtime.


StatefulSet deployment: This strategy is used for stateful applications, such as databases or other applications that require unique identities or persistent storage. StatefulSet ensures that each instance of the application has a unique identity and that they are deployed and scaled in a predictable manner.


DaemonSet deployment: This strategy is used to ensure that a copy of a pod is running on each node in a Kubernetes cluster. DaemonSet is commonly used for applications such as log collectors, monitoring agents, or network proxies.


Helm deployment: Helm is a package manager for Kubernetes that simplifies application deployment and management. It allows you to define, install, and upgrade applications using charts, which are pre-configured templates for Kubernetes resources.


Each deployment strategy has its own advantages and disadvantages, and the choice of strategy depends on the specific needs of the application

Comments

Post a Comment

Popular posts from this blog

Delploy Cluster : Managed K8 & Self Managed K8

Self Managed K8 & Managed K8  In a self-managed Kubernetes cluster, the user is responsible for managing almost every aspect of the cluster. Here are the main components that need to be managed by users: 1. Control Plane Components : Kube-apiserver : The API server is the central management point of the Kubernetes cluster. Users are responsible for setting up, configuring, and managing its availability and performance. Etcd : The key-value store used by Kubernetes for all cluster data. Users need to manage the deployment, backup, scaling, and recovery of etcd . Kube-scheduler : This component is responsible for scheduling pods on available nodes. Users manage its configuration and ensure it runs reliably. Kube-controller-manager : This component runs controller processes that handle replication, node management, endpoints, etc. Users are responsible for managing these controllers. 2. Worker Nodes Components : Kubelet : This agent runs on each worker node and is responsible for ...
Read more

ctr | nerdctl | crictl

The Open Container Initiative (OCI) is a project under the Linux Foundation that aims to create open standards for container formats and runtimes. It was established in June 2015 by Docker, CoreOS, and other leaders in the container industry OCI has developed three key specifications: Runtime Specification (runtime-spec) : Defines how to run a container's filesystem bundle. Image Specification (image-spec) : Standardizes the format for container images. Distribution Specification (distribution-spec) : Provides an API protocol for distributing container content  The initiative also includes tools like runc , which is a reference implementation of the runtime-spec ctr, nerdctl, and crictl: Understanding Their Roles in the Container Ecosystem When working with containers, there are several tools available for interacting with container runtimes like containerd and Kubernetes. ctr , nerdctl , and crictl are three such tools, each serving different purposes within the container life...
Read more

Deploy To Kubernetes with Jenkins GitOps GitHub Pipeline

Image
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ https://www.youtube.com/watch?v=o4QG_kqYvHk  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Basic Jenkins file for the pipeline. Docker image creation and building pipeline {     agent any     environment {         ECR_REPOSITORY = 'your-ecr-repository'         GITOPS_REPO_URL = 'https://github.com/your-gitops-repo.git'         GITOPS_REPO_CREDENTIALS = credentials('your-gitops-credentials-id')     }     stages {         stage('Build Docker Image') {             steps {                 script {         ...
Read more