Saddam ZEMMALI ☁ 🐧 🐳 ☸️ ⛵️

✅update K8S cluster 1. **Check Compatibility and Prepare for the Upgrade**: - Review the release notes of the new Kubernetes version to understand any breaking changes. - Ensure that your current version is compatible with the version you're upgrading to (Kubernetes supports only one minor version skew between components). 2. **Backup Important Data**: - Backup your etcd data, as it contains the cluster state. - Backup any persistent volume data and application-specific data. 3. **Update the Cluster Control Plane (Master Nodes)**: - **Kubeadm**: If you used kubeadm to set up your cluster, you can upgrade the control plane nodes using the kubeadm upgrade command. 🔗sudo kubeadm upgrade plan 🔗sudo kubeadm upgrade apply - **Manual**: For a manually configured control plane, follow the Kubernetes documentation to update each component (etcd, kube-apiserver, kube-controller-manager, kube-scheduler). 4. **Update kubelet and kubectl**: - Update kubelet and kubectl on the control plane nodes. sudo apt-get update && sudo apt-get install -y kubelet=<version> kubectl=<version> sudo systemctl restart kubelet 5. **Drain and Upgrade Worker Nodes**: - Drain each worker node to safely evict all pods. kubectl drain <node-name> --ignore-daemonsets - Upgrade the kubeadm package. sudo apt-get update && sudo apt-get install -y kubeadm=<version> sudo kubeadm upgrade node - Upgrade the kubelet and kubectl packages on the worker nodes. sudo apt-get update && sudo apt-get install -y kubelet=<version> kubectl=<version> sudo systemctl restart kubelet - Uncordon the node to make it schedulable again. kubectl uncordon <node-name> 6. **Verify the Upgrade**: - Ensure all nodes are updated and running the new version. kubectl get nodes - Check the status of your workloads and ensure everything is functioning correctly. #Example Upgrade with kubeadm 1. **Prepare and Plan the Upgrade**: sudo kubeadm upgrade plan 2. **Apply the Control Plane Upgrade**: sudo kubeadm upgrade apply v1.21.0 3. **Upgrade kubelet and kubectl on Control Plane Nodes**: sudo apt-get update && sudo apt-get install -y kubelet=1.21.0-00 kubectl=1.21.0-00 sudo systemctl restart kubelet 4. **Drain, Upgrade, and Uncordon Worker Nodes**: kubectl drain <node-name> --ignore-daemonsets sudo apt-get update && sudo apt-get install -y kubeadm=1.21.0-00 sudo kubeadm upgrade node sudo apt-get update && sudo apt-get install -y kubelet=1.21.0-00 kubectl=1.21.0-00 sudo systemctl restart kubelet kubectl uncordon <node-name> 5. **Verify the Upgrade**: kubectl get nodes Each environment can have its own specific steps based on the setup and configurations.

٦٦

Creating infrastructure for multiple Environments using #terraform with Modular Approach. Environments(Root Module) : DEV, STAGE, PROD. Using #hybird_approach to avoid complexity in managing different env and their statefiles 1 ) Terraform Workspace - use command : terraform workspace new <ENV name> 2 ) File_layout - Create folder for each environment . (eg DEV, PROD..) - To isolate the statefile Each contains: - backend.tf : Configures the backend for storing the Terraform state. - main.tf : Main configuration file for the environment. - terraform.tfvars : Environment-specific variable values Shared Module: 1 ) contains all the configuration files (main.tf, providers.tf, security-group.tf, variables.tf, vpc-subnet.tf ) steps: 1 ) terraform workspace select DEV 2 ) cd DEV/ 3 ) terraform init (to initialize backend and provider) 4 ) terraform plan && terraform apply 5 ) create seperate folders for each environment in backend S3 bucket to #isolate_the_state_file. Advantages: 1 ) Modularity: Reusable code across different environments makes the infrastructure more maintainable and scalable. 2 ) Environment Isolation: Changes in one environment do not affect others, ensuring safe testing and deployment. 3 ) Readability and Organization: A clear structure makes it easier to understand and manage the infrastructure code. Repo : https://lnkd.in/g9Y-jjEQ Happy_Learning !

٤٠٦

١٨ تعليق

OpenShift GitOps OpenShift GitOps is an operator that manages Argo CD in OpenShift clusters. Argo CD is a tool that can synchronize Kubernetes resources to definitions that are stored in Git repositories. Cluster administrators can use OpenShift GitOps to create Argo CD instances with specific access rights. Administrators can create an Argo CD instance that can manage specific namespaces and grant specific users access to the instance. With these instances, teams can be autonomous in deploying applications to specific namespaces. OpenShift GitOps also includes a default administrative Argo CD instance that can manage Kubernetes resources that require administrative access, such as non-namespaced resources or authentication resources. OpenShift administrators can use Argo CD instances with these configurations to manage the cluster itself. Argo CD uses the concept of applications. An application is an Argo CD resource that references a Git repository with Kubernetes resource definitions. Users can create and manage Argo CD applications from the web console or with the Kubernetes API. Applications define a synchronization policy. Argo CD can detect and synchronize changes automatically, or users can trigger synchronizations on demand. The Argo CD web console displays the status of application resources graphically. This representation includes both the resources that are defined in the application, and resources that are related to the application. For example, for an application that contains an operator subscription, the Argo CD web console also shows the install plans, operator workloads, and other related resources. With OpenShift GitOps, cluster administrators can restrict permissions so that only Argo CD instances can update cluster resources, and Git repositories fully describe the intended cluster state. Even if other processes can modify the cluster state, Argo CD can detect and address issues with drift. Additionally, cluster administrators might use Argo CD to manage multiple clusters from the same cluster definition. Besides testing, having a cluster definition can help with other tasks, such as sharing resource definitions between clusters. #GitOps #OpenShift #Kubernetes #k8s #ArgoCD

٢٠

🛠 Essential Azure CLI Commands for DevOps Engineers 🛠 📌 Setup and Configuration: # Install Azure CLI curl -sL https://lnkd.in/dWvfXSsn | sudo bash # Login to Azure az login # Set default subscription az account set --subscription <subscription-id> 📌 Resource Groups: # List resource groups az group list # Create resource group az group create --name <resource-group-name> --location <location> # Delete resource group az group delete --name <resource-group-name> --yes --no-wait 📌 VM Management: # List VMs az vm list # Create VM az vm create --resource-group <resource-group-name> --name <vm-name> --image <image> --admin-username <username> --admin-password <password> # Start VM az vm start --resource-group <resource-group-name> --name <vm-name> # Stop VM az vm stop --resource-group <resource-group-name> --name <vm-name> 📌 Storage Accounts: # List storage accounts az storage account list # Create storage account az storage account create --name <account-name> --resource-group <resource-group-name> --location <location> --sku <sku> # Delete storage account az storage account delete --name <account-name> --resource-group <resource-group-name> 📌 Azure Kubernetes Service (AKS): # List AKS clusters az aks list # Create AKS cluster az aks create --resource-group <resource-group-name> --name <cluster-name> --node-count <node-count> --enable-addons monitoring --generate-ssh-keys # Get AKS credentials az aks get-credentials --resource-group <resource-group-name> --name <cluster-name> 📌 App Services: # List App Services az webapp list # Create App Service az webapp create --resource-group <resource-group-name> --plan <app-service-plan> --name <app-name> --runtime <runtime> # Delete App Service az webapp delete --resource-group <resource-group-name> --name <app-name> 📌 Azure DevOps: # List Azure DevOps organizations az devops organization list # Create Azure DevOps project az devops project create --name <project-name> --organization <organization-url> # List Azure DevOps pipelines az pipelines list --organization <organization-url> --project <project-name> # Run Azure DevOps pipeline az pipelines run --name <pipeline-name> --organization <organization-url> --project <project-name> 📌 Azure Monitor: # List monitor activity logs az monitor activity-log list # Create alert rule az monitor metrics alert create --name <alert-name> --resource-group <resource-group-name> --scopes <resource-id> --condition "<condition>" --action <action-group-id> 🔗 For more detailed commands and options, refer to the Azure CLI Command Reference

٣٣

٢ تعليق

Efficient usage of Terraform Modules for each environment with specific infrastructure without duplication of our code. #Terraform #Cloud #cloudengineer #devopsengineer

٨

⭐ Stress Test ⭐ During my journey, I had to use "Stress test" to test a lot of server resources such as : CPU, memory, file systems and disks. Recently, I had to use "ndisk64" to test new "Flash system" storage disks I/O and performance. The most fun part of this tool that it gives you a variety of variables can be added to your test scenario making it almost similar to the actual environment setup, such as: bandwidth , block size , R/W ratio and etc... You can find out more about "ndisk64" binary -it is part of the nstress tools- from the link below: https://lnkd.in/e_KiiURz #IBM

٣٣

How to create and use Terraform Modules from scratch. Watch the playlist of DevOps Zero To Hero.

١٨

١ تعليق واحد

Nginx vs Apache Performance (Latency - Throughput - Saturation - Availability | HTTP/2 - TLS - Gzip) #nginx #apache #devops https://lnkd.in/enasA7aY

٧٨

٢ تعليق

“Behing every smooth running web application is a load balancer working tirelessly to keep things running smoothly.” But do you know which type to use and why ? Here’s a short guide to help you decide.

٨

𝐓𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐂𝐨𝐦𝐦𝐚𝐧𝐝 𝐋𝐢𝐧𝐞𝐬 [ 𝐒𝐡𝐚𝐫𝐞 𝐭𝐡𝐢𝐬 𝐏𝐨𝐬𝐭 𝐚𝐧𝐝 𝐒𝐚𝐯𝐞 ] terraform fmt #format code per HCL canonical standard terraform validate #validate code for syntax terraform validate -backend=false #validate code skip backend validation terraform init #initialize directory, pull down providers terraform init -get-plugins=false #initialize directory, do not download plugins terraform init -verify-plugins=false #initialize directory, do not verify plugins for Hashicorp signature terraform apply --auto-approve #apply changes without being prompted to enter "yes" terraform destroy --auto-approve #destroy/cleanup deployment without being prompted for “yes” terraform plan -out plan.out #output the deployment plan to plan.out terraform apply plan.out #use the plan.out plan file to deploy infrastructure terraform plan -destroy #outputs a destroy plan terraform apply -target=aws_instance.my_ec2 #only apply/deploy changes to the targeted resource terraform apply -var my_region_variable=us-east-1 #pass a variable via command-line while applying a configuration terraform apply -lock=true #lock the state file so it can't be modified by any other Terraform apply or modification action(possible only where backend allows locking) terraform apply refresh=false # do not reconcile state file with real-world resources(helpful with large complex deployments for saving deployment time) terraform apply --parallelism=5 #number of simultaneous resource operations terraform refresh #reconcile the state in Terraform state file with real-world resources terraform providers #get information about providers used in current configuration terraform state show aws_instance.my_ec2 #show details stored in Terraform state for the resource terraform state pull > terraform.tfstate #download and output terraform state to a file terraform state mv aws_iam_role.my_ssm_role module.custom_module #move a resource tracked via state to different module terraform state replace-provider hashicorp/aws registry.custom.com/aws #replace an existing provider with another terraform state list #list out all the resources tracked via the current state file terraform state rm aws_instance.myinstace #unmanage a resource, delete it from Terraform state file If you are fresher/experienced then do checkout these links 𝐅𝐫𝐞𝐞 𝐜𝐨𝐮𝐫𝐬𝐞𝐬 𝐢𝐧 𝐃𝐞𝐯𝐎𝐩𝐬 - https://lnkd.in/gkB27ZDF 𝐅𝐑𝐄𝐄 𝐃𝐞𝐯𝐎𝐩𝐬/𝐒𝐑𝐄 𝐦𝐞𝐧𝐭𝐨𝐫𝐬𝐡𝐢𝐩 - https://t.me/freebootcamp7 [ Join this telegram group ] 𝐄𝐧𝐫𝐨𝐥𝐥 𝐏𝐑𝐈𝐌𝐄 𝐁𝐀𝐓𝐂𝐇 www.heydevops.in [ Recorded and Live sessions ]

٣١١

١٤ تعليق

✅Terraform commands used on a daily basis: ✨ 1. terraform init: - Initializes a working directory containing Terraform configuration files. 2. terraform plan: - Generates an execution plan, outlining actions Terraform will take. 3. terraform apply: - Applies the changes described in the Terraform configuration. 4. terraform destroy: - Destroys all resources described in the Terraform configuration. 5. terraform validate: - Checks the syntax and validity of Terraform configuration files. 6. terraform refresh: - Updates the state file against real resources in the provider. 7. terraform output: - Displays the output values from the Terraform state. 8. terraform state list: - Lists resources within the Terraform state. 9. terraform show: - Displays a human -readable output of the current state or a specific resource’s state. 10. terraform import: - Imports existing infrastructure into Terraform state. 11. terraform fmt: - Rewrites Terraform configuration files to a canonical format. 12. terraform graph: - Generates a visual representation of the Terraform dependency graph. 13. terraform providers: - Prints a tree of the providers used in the configuration. 14. terraform workspace list: - Lists available workspaces. 15. terraform workspace select: - Switches to another existing workspace. 16. terraform workspace new: - Creates a new workspace. 17. terraform workspace delete: - Deletes an existing workspace. 18. terraform output: - Retrieves output values from a module. 19. terraform state mv: - Moves an item in the state. 20. terraform state pull: - Pulls the state from a remote backend. 21. terraform state push: - Pushes the state to a remote backend. 22. terraform state rm: - Removes items from the state. 23. terraform taint: - Manually marks a resource for recreation. 24. terraform untaint: - Removes the ‘tainted’ state from a resource. 25. terraform login: - Saves credentials for Terraform Cloud. 26. terraform logout: - Removes credentials for Terraform Cloud. 27. terraform force -unlock: - Releases a locked state. 28. terraform import: - Imports existing infrastructure into your Terraform state. 29. terraform plan -out: - Saves the generated plan to a file. 30. terraform apply -auto -approve: - Automatically applies changes without requiring approval. 31. terraform apply -target=resource: - Applies changes only to a specific resource. 32. terraform destroy -target=resource: - Destroys a specific resource. 33. terraform apply -var=”key=value”: - Sets a variable’s value directly in the command line. 34. terraform apply -var -file=filename.tfvars: - Specifies a file containing variable definitions. 35. terraform apply -var -file=filename.auto.tfvars: - Automatically loads variables from a file.

٣

١ تعليق واحد

🚀 Deploying Microservices on Azure Kubernetes Service (AKS) Kubernetes has revolutionized application deployment. Here's a snapshot of how to effectively run microservices on AKS: 🔍 Key Components: - AKS Cluster: The core infrastructure. - Virtual Network: Ensures secure, isolated communication. - Ingress Controller: Manages traffic routing. - Azure Load Balancer: Distributes traffic evenly. - Azure Container Registry: Stores Docker images securely. - Azure Pipelines: Automates CI/CD for seamless updates. - Helm: Simplifies deployment management. - Azure Monitor: Provides critical health insights. 🛠️ Deployment Steps: 1. Create an AKS Cluster. 2. Set up a Virtual Network. 3. Deploy the Ingress Controller and configure Load Balancer. 4. Push images to Azure Container Registry. 5. Use Helm to deploy and manage your microservices. Scalable, secure, and cloud-native. What’s your take on deploying microservices on AKS or other platforms? Let’s discuss! 🌐 #DevOps #Kubernetes #AKS #CloudNative #MyceliumWeb

٨

When you create a Kubernetes cluster with say, a bootstrap method like Kubeadm, there are a few static Pods that get created. For example, the API server and Etcd. These static Pods receive IP addresses from the host network, not the internal Pod network with the CNI. In fact, the Control Plane itself when accessed typically hits the API server, which is another reason why it’s so drastically important to ensure that the host network is running as expected. When you run Kubeadm as your bootstrapper, you’re specifying the host network where the control plane is running. That’s how the API server is accessed. The Kubernetes maintainers recommend to setup the host network so that the default gateway IP is the one that Kubernetes components auto-detect and use from the host network. #kubernetes #devops #platformengineering

٦٣

١ تعليق واحد

🤯 How does Kubernetes traffic routing compare to #istio traffic routing? ⬇️ Here is an easy-to-understand overview:️ ⬇️ Plain 𝑲𝒖𝒃𝒆𝒓𝒏𝒆𝒕𝒆𝒔: Kubernetes traffic routing is implemented using Ingress, Service and Pod resources. 1️⃣ 𝐏𝐨𝐝 Pods are the smallest units managed directly by Kubernetes. When deploying applications in plain Kubernetes, application ports are exposed by containers running in Pods. 2️⃣ 𝐒𝐞𝐫𝐯𝐢𝐜𝐞 Services are in general used to expose Pods to other applications running inside the Kubernetes cluster. A plain Kubernetes Service adds, as its endpoints, all Pods which match its label selector. It provides a rudimentary load balancing of incoming requests following a random choice round-robin policy. 3️⃣ 𝐈𝐧𝐠𝐫𝐞𝐬𝐬 An Ingress is used to expose Services to clients outside the Kubernetes cluster. It can provide additional functionality such as TLS termination. 𝑰𝒔𝒕𝒊𝒐: Using service meshes like Istio, does not mean that you should stop using Kubernetes primitives. In order to direct traffic within the mesh, Istio still needs to know where all your endpoints (Pods) are, and which Services they belong to. Therefore, Istio utilises Kubernetes native service discovery system to populate its own service registry. 1️⃣ 𝐄𝐧𝐯𝐨𝐲 𝐏𝐫𝐨𝐱𝐲 When using Istio service mesh, Envoy Proxy runs as an additional container in every Pod, following a so-called sidecar pattern. All traffic sent and received by applications is proxied through Envoy, simplifying the way how you direct and control traffic inside your mesh without introducing changes to your application components. Virtual services, along with destination rules, are the basic building blocks of Istio’s traffic routing functionality. 2️⃣ 𝐃𝐞𝐬𝐭𝐢𝐧𝐚𝐭𝐢𝐨𝐧 𝐑𝐮𝐥𝐞 Istio destination rules allow defining subsets of endpoints based on specific labels, as well as using tailored load balancing policies. 3️⃣ 𝐕𝐢𝐫𝐭𝐮𝐚𝐥 𝐒𝐞𝐫𝐯𝐢𝐜𝐞 Virtual services extend the functionality of Kubernetes Services by enabling you to define sophisticated traffic distribution rules, based on, for example, URI or HTTP headers. 4️⃣ 𝐆𝐚𝐭𝐞𝐰𝐚𝐲 Gateways handle the incoming and outgoing traffic from/to outside the Kubernetes cluster. In principle, they play a similar role to the plain Kubernetes Ingresses, running at the edge of the service mesh. However, they enable you to use the full potential and flexibility of Istio’s traffic routing seamlessly merging with virtual service functionality. ___ My name is Jakub Krzywda, PhD. I post about: #kubernetes, #cloudnative technologies and #devops practices. #K8sWithK5a Click my name + follow + 🔔 so you don’t miss my next posts! Looking for training in Kubernetes or other Cloud Native technologies? 🔝 Check courses I teach (link on the top of my profile)

٩٧

٧ تعليق

🚀 Easy Tips for Using Functions in Bash Scripting 🚀 What Are Functions? 🤔 Functions are blocks of code that help you avoid repeating the same commands. They make your scripts cleaner and easier to manage. How to Define Functions 📝 You can define functions in two simple ways: function name() { ... } name() { ... } Reuse Your Code 🔄 Define a function once, and call it whenever you need it. This saves you from writing the same code over and over. Local vs. Global Variables 🌍🔒 Global Variables are accessible everywhere in your script. Local Variables are only available within the function. Use local to create them. Pass Arguments 🎯 You can send data into functions, so they work with different inputs. For example, function_name arg1 arg2. Get Return Values 🔙 Functions can return values that you can use later in your script. Note: Return values are typically integers. Organize Your Script 🗂️ Break up large scripts into functions to keep your code tidy and easier to read. Make your Bash scripts smart and efficient with functions! 💡✨ #BashScripting #CodingTips #TechHacks #Programming #CodeSmart

٨