Kubernetes File Structure

 kubernetes-repo/

├── charts/

│   ├── mongodb/

│   │   ├── Chart.yaml

│   │   ├── values.yaml

│   │   ├── values-dev.yaml

│   │   ├── values-test.yaml

│   │   ├── values-uat.yaml

│   │   ├── values-prod.yaml

│   │   └── templates/

│   │       ├── deployment.yaml

│   │       ├── service.yaml

│   │       ├── ingress.yaml

│   │       └── configmap.yaml

│   ├── logstash/

│   │   ├── Chart.yaml

│   │   ├── values.yaml

│   │   ├── values-dev.yaml

│   │   ├── values-test.yaml

│   │   ├── values-uat.yaml

│   │   ├── values-prod.yaml

│   │   └── templates/

│   │       ├── deployment.yaml

│   │       ├── service.yaml

│   │       ├── configmap.yaml

│   │       └── secret.yaml

│   ├── app/

│   │   ├── Chart.yaml

│   │   ├── values.yaml

│   │   ├── values-dev.yaml

│   │   ├── values-test.yaml

│   │   ├── values-uat.yaml

│   │   ├── values-prod.yaml

│   │   └── templates/

│   │       ├── deployment.yaml

│   │       ├── service.yaml

│   │       ├── ingress.yaml

│   │       ├── configmap.yaml

│   │       └── secret.yaml

├── manifests/

│   ├── dev/

│   │   ├── mongodb-deployment.yaml

│   │   ├── logstash-deployment.yaml

│   │   └── app-deployment.yaml

│   ├── test/

│   │   ├── mongodb-deployment.yaml

│   │   ├── logstash-deployment.yaml

│   │   └── app-deployment.yaml

│   ├── uat/

│   │   ├── mongodb-deployment.yaml

│   │   ├── logstash-deployment.yaml

│   │   └── app-deployment.yaml

│   └── prod/

│       ├── mongodb-deployment.yaml

│       ├── logstash-deployment.yaml

│       └── app-deployment.yaml

├── scripts/

│   ├── deploy.sh

│   ├── update.sh

│   └── rollback.sh

├── README.md

└── .gitignore




Pipeline for the above

trigger:
  branches:
    include:
      - main  # Branch that triggers the pipeline

pool:
  vmImage: 'ubuntu-latest'  # Use the latest Ubuntu VM image

variables:
  azureSubscription: '$(azureSubscription)'  # Azure service connection
  kubernetesCluster: '$(kubernetesCluster)'  # Kubernetes cluster name
  helmChartPath: './charts/app'  # Path to Helm chart
  releaseName: 'my-release'  # Helm release name
  rollbackRevision: 1  # Revision to rollback to if needed

parameters:
  - name: environment
    type: string
    default: 'all'  # Default to 'all' to deploy to all environments
    values:
      - dev
      - test
      - uat
      - prod
      - all

stages:
  - stage: Deploy
    displayName: Deploy to Environments
    jobs:
      - job: DeployToEnvironments
        steps:
          - ${{ if eq(parameters.environment, 'dev') }}:
            - task: UseHelm@1
              inputs:
                command: 'upgrade'
                arguments: '--install $(releaseName) $(helmChartPath) --values $(helmChartPath)/values-dev.yaml --namespace dev'

          - ${{ if eq(parameters.environment, 'test') }}:
            - task: UseHelm@1
              inputs:
                command: 'upgrade'
                arguments: '--install $(releaseName) $(helmChartPath) --values $(helmChartPath)/values-test.yaml --namespace test'

          - ${{ if eq(parameters.environment, 'uat') }}:
            - task: UseHelm@1
              inputs:
                command: 'upgrade'
                arguments: '--install $(releaseName) $(helmChartPath) --values $(helmChartPath)/values-uat.yaml --namespace uat'

          - ${{ if eq(parameters.environment, 'prod') }}:
            - task: UseHelm@1
              inputs:
                command: 'upgrade'
                arguments: '--install $(releaseName) $(helmChartPath) --values $(helmChartPath)/values-prod.yaml --namespace prod'

          - ${{ if eq(parameters.environment, 'all') }}:
            - task: UseHelm@1
              inputs:
                command: 'upgrade'
                arguments: '--install $(releaseName) $(helmChartPath) --values $(helmChartPath)/values-dev.yaml --namespace dev'

            - task: UseHelm@1
              inputs:
                command: 'upgrade'
                arguments: '--install $(releaseName) $(helmChartPath) --values $(helmChartPath)/values-test.yaml --namespace test'

            - task: UseHelm@1
              inputs:
                command: 'upgrade'
                arguments: '--install $(releaseName) $(helmChartPath) --values $(helmChartPath)/values-uat.yaml --namespace uat'

            - task: UseHelm@1
              inputs:
                command: 'upgrade'
                arguments: '--install $(releaseName) $(helmChartPath) --values $(helmChartPath)/values-prod.yaml --namespace prod'

  - stage: Rollback
    dependsOn: Deploy
    condition: failed('Deploy')
    jobs:
      - job: RollbackDeployment
        steps:
          - task: AzureCLI@2
            inputs:
              azureSubscription: '$(azureSubscription)'
              scriptType: 'bash'
              scriptPath: 'rollback.sh'
              arguments: '--revision $(rollbackRevision)'

Comments

Post a Comment

Popular posts from this blog

Kube-Proxy : Configure Production Grade Cluster

Configuring kube-proxy involves setting up its behavior for managing network traffic within a Kubernetes cluster. Here's a general guide: 1. Understand kube-proxy Modes kube-proxy supports two main modes for handling traffic: iptables Mode: Uses Linux iptables for routing traffic. It's simple and widely supported. IPVS Mode: Uses Linux Virtual Server (IPVS) for advanced load balancing and connection tracking. Configuring iptables mode for kube-proxy involves setting up network rules to route traffic efficiently within a Kubernetes cluster. Here's a step-by-step guide: Step 1: Verify kube-proxy Mode By default, kube-proxy operates in iptables mode . To confirm this: kubectl get configmap kube-proxy -n kube-system -o yaml Look for the mode field in the configuration file. Step 2: Modify kube-proxy Configuration If kube-proxy is not in iptables mode, update its configuration: Edit the kube-proxy ConfigMap: kubectl edit configmap kube-proxy -n kube-system Set the proxy-mod...
Read more

Networking : How is the Kubernetes networking done CNI is after cluster is running

 In Kubernetes, networking can be set up at different stages, depending on your requirements and the tools you're using. Here's a breakdown: 1. During Provisioning (e.g., via Terraform): VPC/Network Setup: When you're provisioning your infrastructure (e.g., on AWS, Azure, GCP) using Terraform, you'll typically set up the underlying network components first. This includes creating Virtual Private Clouds (VPCs), subnets, security groups, routing tables, etc. These components define the network within which your Kubernetes cluster will operate. Cluster Networking Configuration: When you provision a Kubernetes cluster using Terraform, you might also configure networking settings such as: Pod CIDR: The range of IP addresses for Pods. Service CIDR: The range of IP addresses for services. Network Policies: To control the communication between pods. 2. After Provisioning: CNI Plugin Installation: Once the cluster is up and running, you need to set up the container network...
Read more

Laptop : Configure your laptop to connect to AKS - Azure

To configure your laptop to connect to an Azure Kubernetes Service (AKS) cluster, follow these steps: Install Prerequisites Azure CLI: Install the Azure CLI to interact with Azure resources. For installation instructions, visit Azure CLI Installation Guide . kubectl: Install the Kubernetes CLI tool to manage your AKS cluster. Install it using Azure CLI: az aks install-cli Authenticate with Azure Log in to your Azure account using the Azure CLI: az login If you have multiple subscriptions, set the desired subscription: az account set --subscription "<subscription-id>" Connect to the AKS Cluster Retrieve the cluster credentials and configure kubectl : az aks get-credentials --resource-group <resource-group-name> --name <aks-cluster-name> This command downloads the kubeconfig file and sets up kubectl to interact with the cluster. Verify the Connection Check the nodes in your AKS cluster: kubectl get nodes Optional: Use Azure Cloud Shell If you prefer not to ...
Read more