Ayush S.

Complete Helm Chart Tutorial: From Beginner to Expert Guide in 20 minutes || Kubernetes Free Series https://lnkd.in/gTXpVzfS Helm is a package manager for Kubernetes. Think of it as the "apt" or "yum" of the Kubernetes world. It helps you manage Kubernetes applications more efficiently. Helm Charts are the packages themselves. These charts are essentially templates that describe a Kubernetes application. They contain all the necessary files and configurations to deploy a specific application, including: YAML manifests: These define the Kubernetes resources needed for the application, such as Deployments, Services, ConfigMaps, and Secrets. Templates: These allow you to parameterize your charts, making them more flexible and reusable across different environments. Values files: These files hold the values for the parameters defined in the templates. Key Benefits of Using Helm Charts: Simplified deployment: Helm charts package up the complexity of deploying Kubernetes applications, making it easier for developers and operations teams. Version control: Charts can be versioned, allowing you to track changes and manage different releases. Reusability: Charts can be shared and reused, reducing the need to create new manifests from scratch. Configuration management: Helm charts make it easier to manage configurations for different environments. Dependency management: Helm can handle dependencies between charts, ensuring that all required components are deployed together. How Helm Charts Work: Create a chart: You can create a new chart using the helm create command. This will generate a basic chart structure. Customize the chart: You'll edit the YAML manifests and templates to define the resources and parameters for your application. Package the chart: Use the helm package command to package the chart into a .tgz file. Install the chart: Deploy the chart to your Kubernetes cluster using the helm install command. You can provide values for the parameters defined in the chart. In essence, Helm charts provide a convenient way to package, deploy, and manage Kubernetes applications, making the process more efficient and less error-prone. Want to be the part of free kubernetes series?? Check here - https://lnkd.in/gTXpVzfS

243

5 Comments

𝐏𝐨𝐬𝐭 30 🚀 𝐓𝐢𝐭𝐥𝐞: Mastering Node Maintenance in Kubernetes with Cordoning, Draining, and Uncordoning 🛠️🚀 🔍 𝐈𝐬𝐬𝐮𝐞: Performing maintenance on Kubernetes nodes without impacting running workloads can be challenging. If not handled properly, it can lead to application downtime or degraded performance. 💡𝐅𝐢𝐱: Kubernetes provides a set of powerful commands—kubectl cordon, kubectl drain, and kubectl uncordon—to manage node maintenance effectively. These commands help ensure that workloads are safely moved and maintained during node updates or repairs. 📋 𝐄𝐱𝐚𝐦𝐩𝐥𝐞:  1. 𝐂𝐨𝐫𝐝𝐨𝐧𝐢𝐧𝐠 𝐚 𝐍𝐨𝐝𝐞: The kubectl cordon command marks a node as un-schedulable, preventing any new pods from being scheduled on it. $ kubectl cordon <node-name> This command helps you prepare the node for maintenance without affecting currently running pods. 2. 𝐃𝐫𝐚𝐢𝐧𝐢𝐧𝐠 𝐚 𝐍𝐨𝐝𝐞: The kubectl drain command evicts all pods from a node, ensuring that they are safely moved to other nodes in the cluster. $ kubectl drain <node-name> --ignore-daemonsets  This command is crucial for safely relocating workloads and ensuring minimal disruption during node maintenance. 3. 𝐔𝐧𝐜𝐨𝐫𝐝𝐨𝐧𝐢𝐧𝐠 𝐚 𝐍𝐨𝐝𝐞: After maintenance is complete, use the kubectl uncordon command to mark the node as schedulable again, allowing new pods to be placed on it. $ kubectl uncordon <node-name> This command brings the node back into service, ready to host new workloads. 🎓 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠s: 1. Safe Maintenance: Using cordon and drain ensures that node maintenance is carried out without disrupting running applications. 2. Efficient Workload Management: These commands allow for the seamless relocation of pods, maintaining application availability and performance. Mastering these Kubernetes commands empowers you to perform node maintenance confidently, ensuring that your applications remain highly available and performant. #Kubernetes #DevOps #NodeMaintenance #CloudComputing #K8s #TechTips #Reliability #HighAvailability #ClusterManagement 🛠️🚀🔧

41

$ kubectl apply -f ckad-certificate.yaml -n bharath-b-s certificates/ckad-certificate-created I’m absolutely over the moon to announce that I’ve earned my first K8s certification! 🚀 A big thank you to #MumshadMannambeth and #KodeKloud for the course and all the dedicated CKAD challenges and labs. Also, big thanks to killer.sh and #Killercoda for their hands-on exercises that prepped me for the real deal. I’m excited to leverage this knowledge to drive innovation and efficiency in my projects. Onward to new challenges and opportunities in the Kubernetes ecosystem #cncf #kubernetes #devops #cloudnativecomputing #continouslearning #ckad #linuxfoundation #containers #cloud #k8scertified #cloudengineering #softwareengineering #cloudnativearchitecture #KodeKloud #MumshadMannambeth #TechJourney

20

5 Comments

𝐏𝐨𝐬𝐭 35 🚀 𝐓𝐢𝐭𝐥𝐞: Why the Kubeconfig File is Vital in Kubernetes Management 🔐 🔍 𝐈𝐬𝐬𝐮𝐞: Managing access to multiple Kubernetes clusters can quickly become overwhelming without a unified approach. This complexity often leads to misconfigurations, potential security lapses, and operational inefficiencies. 💡𝐅𝐢𝐱: Enter the Kubeconfig file—a powerful configuration file that simplifies Kubernetes management by centralizing cluster, user, and context settings. By default, this file is located at ~/.kube/config. 📝 What's Inside the Kubeconfig File? 1. Cluster: Contains information about the Kubernetes API server (server and certificate-authority-data). 2. User: Stores authentication details like client certificates (client-certificate-data and client-key-data). 3. Context: Combines a cluster and user into a specific working environment 📋 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: Here’s a sample Kubeconfig file and some essential commands To switch between different contexts (clusters or namespaces): $ kubectl config use-context <context-name> To view your current Kubeconfig setup: $ kubectl config view By mastering Kubeconfig, you can ensure secure, error-free, and seamless operations across your Kubernetes environments. #Kubernetes #Kubeconfig #DevOps #CloudNative #K8sBestPractices #InfrastructureAsCode #Automation 𝐌𝐞𝐝𝐢𝐮𝐦𝐏𝐨𝐬𝐭 --> https://lnkd.in/djDMsrYg

100

2 Comments

Automating AWS infrastructure with Terraform is key to unlocking Infrastructure as Code (IaC) capabilities. Check out this basic guide to kickstart your Terraform journey on AWS: 1. **Install Terraform** Download Terraform from the official website, install it on your machine, and ensure accessibility via the command line. 2. **Configure AWS Credentials** Set up AWS credentials to empower Terraform in managing your resources. Configure AWS CLI or utilize environment variables like AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. 3. **Write Terraform Configuration** Create a directory for your Terraform files and add a .tf file (e.g., main.tf) to define resources such as EC2 instances and VPCs. 4. **Initialize Terraform** Initiate Terraform by running 'terraform init' in your directory to download the AWS provider plugin. 5. **Plan and Apply Infrastructure Changes** Preview planned changes with 'terraform plan' and apply them using 'terraform apply' if everything looks good. 6. **Manage Infrastructure Changes** Update your infrastructure by modifying .tf files and reapplying changes with 'terraform apply'. 7. **Destroy Infrastructure** Clean up resources when no longer needed by running 'terraform destroy'. Remember these Best Practices for effective Terraform usage: - **State Management:** Store your state file securely, preferably using AWS S3 with DynamoDB for state locking in production. - **Modules:** Create reusable components with modules for organizational clarity and scalability. - **Version Control:** Collaborate efficiently by storing Terraform configuration files in version control like Git. Terraform provides the flexibility and robustness needed to automate infrastructure seamlessly at scale. #Terraform #AWS #InfrastructureAutomation

3

𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 𝐏𝐫𝐨𝐝𝐮𝐜𝐭𝐢𝐨𝐧 𝐞𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭 The DevOps/SRE engineer always are responsible to handle the production issues and to save your from any escalation this post is curated: 𝐀𝐯𝐚𝐢𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲 : A single-machine Kubernetes learning environment has a single point of failure. Creating a highly available cluster means considering: - Separating the control plane from the worker nodes. - Replicating the control plane components on multiple nodes. - Load balancing traffic to the cluster’s API server. - Having enough worker nodes available, or able to quickly become available, as changing workloads warrant it. 𝐒𝐜𝐚𝐥𝐞 : If you expect your production Kubernetes environment to receive a stable amount of demand, you might be able to set up for the capacity you need and be done. However, if you expect demand to grow over time or change dramatically based on things like season or special events, you need to plan how to scale to relieve increased pressure from more requests to the control plane and worker nodes or scale down to reduce unused resources. 𝐒𝐞𝐜𝐮𝐫𝐢𝐭𝐲 𝐚𝐧𝐝 𝐚𝐜𝐜𝐞𝐬𝐬 𝐦𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 : You have full admin privileges on your own Kubernetes learning cluster. But shared clusters with important workloads, and more than one or two users, require a more refined approach to who and what can access cluster resources. You can use role-based access control (RBAC) and other security mechanisms to make sure that users and workloads can get access to the resources they need, while keeping workloads, and the cluster itself, secure. You can set limits on the resources that users and workloads can access by managing policies and container resources. If you need any help on your job search then join do checkout the prime batch8 exclusive on DevOps/SRE content 𝐖𝐡𝐲 𝐭𝐡𝐢𝐬 𝐃𝐞𝐯𝐎𝐩𝐬 𝐂𝐨𝐮𝐫𝐬𝐞 by Praveen Singampalli ?? 📌Easy to learn with 14 projects 📌The best in DevOps tools included for 2024 📌Mock interviews/resume reviews/doubts session 📌Live Classes/recorded sessions 📌Each session backed by a project 📌Roles and responsibilities document for each project 📌 More details check here https://lnkd.in/gF2fs6jF 𝐄𝐧𝐫𝐨𝐥𝐥 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐜𝐨𝐮𝐫𝐬𝐞 : https://lnkd.in/gF2fs6jF [Classes starting in 1 week] 

280

9 Comments

"Certified Kubernetes Administrator (CKA) Exam Guide" by #Packt Books has become my indispensable companion in navigating the complexities of Kubernetes. Author 'Melony Qin' Whether I'm deepening my understanding, revising towards my #CKAexam, or seeking quick solutions in my daily Kubernetes work, this book consistently proves its worth. Its comprehensive coverage, clear explanations, and practical examples make it my go-to resource for learning and mastering Kubernetes. It has easy to read fonts, Simple but concise real-life exampls, From fundamental concepts to advanced topics, this guide and its relevance extends beyond exam preparation, serving as a reliable reference point in my everyday interactions with Kubernetes, making it an essential tool in my professional and in my Education journey.

8

2 Comments

𝐓𝐞𝐫𝐫𝐚𝐟𝐨𝐫𝐦 𝐌𝐨𝐬𝐭 𝐀𝐬𝐤𝐞𝐝 𝐈𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 & 𝐀𝐧𝐬𝐰𝐞𝐫𝐬, 𝐬𝐡𝐚𝐫𝐞 𝐢𝐭 𝐰𝐢𝐭𝐡 𝐲𝐨𝐮𝐫 𝐟𝐫𝐢𝐞𝐧𝐝𝐬 𝐚𝐧𝐝 𝐜𝐨𝐦𝐦𝐮𝐧𝐢𝐭𝐲 𝐭𝐨 𝐬𝐩𝐫𝐞𝐚𝐝 𝐭𝐡𝐞 𝐢𝐝𝐞𝐚𝐬 𝐚𝐧𝐝 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞 Terraform is a powerful tool for provisioning and managing infrastructure as code. Let's explore some common scenarios where Terraform excels: 1. Infrastructure Provisioning Cloud-based resources: Creating and managing resources like EC2 instances, VPCs, S3 buckets, RDS databases, and more on platforms like AWS, Azure, GCP, and others. On-premises infrastructure: Provisioning servers, networks, and storage in data centers using providers like VMware, OpenStack, etc. Infrastructure as a Service (IaaS): Deploying virtual machines and networks in a consistent manner across different cloud providers. 2. Application Deployment Multi-tier applications: Managing the deployment of web servers, application servers, databases, and other components in a coordinated fashion. Microservices architecture: Deploying and scaling individual microservices independently. Container orchestration: Integrating Terraform with Kubernetes to manage clusters and deployments. 3. Configuration Management Network configuration: Defining and managing network components like subnets, security groups, load balancers, and firewalls. Database configuration: Creating and configuring databases, users, and permissions. Application configuration: Managing application-specific settings and parameters. 4. Infrastructure as Code (IaC) Best Practices Version control: Storing Terraform code in a version control system like Git for collaboration and tracking changes. Modularity: Breaking down infrastructure into reusable modules for better organization and reusability. Testing: Writing unit and integration tests for Terraform code to ensure correctness and reliability. State management: Understanding Terraform state and how to manage it effectively. 👉Download the Document from here - https://lnkd.in/gUhAadiF 👉HandsOn terraform project - https://lnkd.in/gkB27ZDF 👉Any queries connect here - https://lnkd.in/dW6GJMiS

453

14 Comments

Most Challenged Kubernetes CrashLoopBackOff Troubleshooting Interview Questions 1. How can you use kubectl commands to get more information about a pod experiencing a CrashLoopBackOff error? 2. You suspect a configuration issue is causing the CrashLoopBackOff error. How would you go about debugging the configuration? 3. A deployment with multiple replicas has some pods stuck in CrashLoopBackOff, while others are running fine. How would you investigate this issue? 4. The logs from the pod indicate a resource limitation (e.g., out of memory). How would you troubleshoot this scenario? 5. You suspect a memory leak is causing CrashLoopBackOff. How can you utilize tools like pprof or gcore within a container to diagnose the issue? 6. How would you troubleshoot a CrashLoopBackOff error caused by compatibility issues between your application and a specific Kubernetes version? #kubernetes #devops #crashloopbackoff #troubleshooting #devopsjobs #hiring #UK #CANADA #USA #interviewquestions #automation

12

1 Comment

𝗡𝗼𝗱𝗲 𝗔𝗳𝗳𝗶𝗻𝗶𝘁𝘆: Node affinity is a key concept in Kubernetes for managing pod placement on nodes. It involves applying labels to nodes and pods to control scheduling based on these labels. 𝗧𝘆𝗽𝗲𝘀 𝗼𝗳 𝗡𝗼𝗱𝗲 𝗮𝗳𝗳𝗶𝗻𝗶𝘁𝘆 :   𝟭)𝗥𝗲𝗾𝘂𝗶𝗿𝗲𝗱𝗗𝘂𝗿𝗶𝗻𝗴𝗦𝗰𝗵𝗲𝗱𝘂𝗹𝗶𝗻𝗴𝗜𝗴𝗻𝗼𝗿𝗲𝗱𝗗𝘂𝗿𝗶𝗻𝗴𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻:   This ensures that pods are scheduled only on nodes with matching labels.  If no suitable node is available, the pod will not be scheduled.  𝟮)𝗣𝗿𝗲𝗳𝗲𝗿𝗿𝗲𝗱𝗗𝘂𝗿𝗶𝗻𝗴𝗦𝗰𝗵𝗲𝗱𝘂𝗹𝗶𝗻𝗴𝗜𝗴𝗻𝗼𝗿𝗲𝗱𝗗𝘂𝗿𝗶𝗻𝗴𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻:   This provides a preference for scheduling on nodes with specific labels but   allows pods to be scheduled on other nodes if necessary. #Kubernetes #NodeAffinity #DevOps #CloudComputing #ContainerOrchestration

26

AWS IAM interview questions* Q.1 what are permissions boundaries?  Constraints defining the maximum permissions an entity can have, used for additional control. - Example of using a permissions boundary:  Restrict developers to non-destructive actions, even if more permissions are granted by policies. Q.2 What is the identity federation in AWS IAM?    Allows external identities (e.g., from Active Directory) to access AWS resources using SAML or OIDC. - Configuring SSO with corporate credentials:  - Integrate AWS SSO with your identity provider (e.g., Active Directory).    - Map users/groups to AWS roles for resource access. Q.3 How to enable cross-account access in AWS?  Use IAM roles with trust policies allowing another account to assume the role. - Setting up a trust relationship:   - Account A (Resource Owner):** Create a role with a trust policy for Account B   - Account B (Requester):** Assume the role using AWS STS. Q.4 What is IAM Access Analyzer?   A tool to identify resources that allow external access and ensure security. Responding to an Access Analyzer alert:   Review the policy, verify necessity, and modify or restrict permissions if needed. Q.5. Why minimize root account access?  The root account has unrestricted access, making it a security risk if compromised. #AWSIAM #AWS #Azure #Terraform #Cloud #IaaS #PaaS #SaaS #IAM #AzureDevOps #Azure #AzureIaaS

6

🎉 Officially Terraform Associate (003) Certified! 🎉 After years of hands-on experience with Terraform, I’ve finally taken the time to complete the official Terraform Associate (003) certification. Excited to continue building and scaling infrastructure with Terraform and explore even more advanced use cases in the cloud space. 🌐 Check out my credential below ⬇️ #Terraform #CloudInfrastructure #DevOps #HashiCorp #ProfessionalGrowth #CertificationJourney

32

7 Comments

Post 21 🚀 𝐓𝐢𝐭𝐥𝐞:  Ensuring Reliability with Static Pods in Kubernetes 🚀 🔍 𝐈𝐬𝐬𝐮𝐞: In certain scenarios, critical services need to be tightly coupled with specific nodes. Traditional pod management methods in Kubernetes might not guarantee the deployment and stability of these essential services directly on designated nodes, which can lead to operational inefficiencies and potential service gaps. 💡𝐅𝐢𝐱: The solution is Static Pods! 🎯 Static Pods are managed directly by the kubelet on a specific node, bypassing the Kubernetes API server. This ensures that the pods are always running on the desired nodes, providing a robust solution for deploying essential, node-specific services. 📋 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: To illustrate, you can define a Pod definition yaml file and to deploy this as a Static Pod, save the YAML file on the node at a specified directory (e.g., /etc/kubernetes/manifests/), (This path can be checked by the config file of kublet which is at location /var/lib/kublet/config.yaml with a line stating the path to static pod) The kubelet will automatically detect and start the Static Pod, ensuring it runs directly on that node. 📂 🎓 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠s: Implementing Static Pods in your Kubernetes clusters provides several key advantages: 1. Node-specific Deployment: Ensure that critical services run on specific nodes without relying on the Kubernetes scheduler. 2. High Availability: Direct management by the kubelet ensures that the pods are always running, even if the API server is down. 3. To identify which is a static pod , check the suffix of the pod name it is appended with the nodename , check the snippet where some pods like "etcd-my-node-1" is static pod as it has node-1 appended to the name and the other pods without a node name suffix are managed by the Kubernetes scheduler. By leveraging Static Pods, you can achieve higher reliability and control for node-specific deployments, ensuring that your critical services are always up and running. #Kubernetes #DevOps #CloudComputing #StaticPods #K8s #TechTips #Infrastructure #Scalability #Reliability 🚀🔧

23

2 Comments

🌟 Understanding Kubernetes Service Accounts: A Quick Guide 📒🚩In Kubernetes, a Service Account is crucial for securely managing the interaction between your pods and the Kubernetes API. 📢It enables pods to authenticate and execute specific actions within the cluster based on assigned permissions. 📢Here’s a simplified breakdown: 🚩ServiceAccount.yaml: Creates a service account named mysa in the default namespace. This account is used by pods to interact with the Kubernetes API securely. 🚩Role.yaml: Defines a role pod-reader that grants permissions to get, watch, and list pods in the default namespace. 🚩RoleBinding.yaml: Binds the mysa service account to the pod-reader role, allowing it to perform the specified actions on pods. 🚩ServiceAccount attached to a Pod: The pod named nginx uses the mysa service account to interact with the Kubernetes API as per the defined role. By using Service Accounts, you can fine-tune the security and permissions within your Kubernetes environment, ensuring that pods only have access to what they need. #Kubernetes #DevOps #CloudNative #Security #ServiceAccount

9

Blue-Green Deployments in Kubernetes Blue-Green Deployments in Kubernetes is a strategy that allows you to roll out changes smoothly, minimize downtime, and mitigate risks associated with software updates. Let’s explore the principles and practices that make up Blue-Green Deployments. 1️⃣ The Challenge of Traditional Deployments: Blue-Green Deployments aim to address service interruptions or errors during the update process by introducing a parallel environment for deploying and testing changes before directing traffic to it. 2️⃣ Principle of Blue-Green Deployments: Blue-Green Deployments maintain two identical environments—Blue (current live version) and Green (new version). Initially, all traffic is directed to the Blue environment. The Green environment is then deployed, and tested, and, upon validation, traffic is switched to it seamlessly. 3️⃣ Infrastructure Setup: Setting up Blue-Green environments involves using separate namespaces, services, and deployments for Blue and Green. 4️⃣ Traffic Switching Strategies: Kubernetes provides various strategies for traffic switching. Gradual traffic shifting—where a percentage of traffic is directed to the Green environment, or immediate cutover—where all traffic is switched once the Green environment is validated. 5️⃣ Service Discovery and Load Balancing: Kubernetes services play a key role in this, ensuring that traffic is directed seamlessly between Blue and Green environments. 6️⃣ Validation and Testing: Automated testing, canary releases, or user acceptance testing (UAT) can be employed to validate the new version. This ensures that the Green environment is stable, and performs well. 7️⃣ Rollback Capability: If issues are detected in the Green environment, traffic can swiftly be redirected back to the Blue environment, minimizing the impact on users and ensuring a quick recovery from unexpected challenges. 8️⃣ Monitoring and Observability: Monitoring tools help track the health and performance of both Blue and Green environments. This visibility is crucial for making informed decisions, validating updates, and ensuring a seamless transition. 9️⃣ Global Rollouts and Scaling: Whether deploying updates regionally or worldwide, the parallel structure of Blue-Green environments accommodates diverse scaling requirements, ensuring consistent and efficient updates across the entire deployment landscape. 🔟 Zero-Downtime Updates: By directing traffic seamlessly between Blue and Green environments, users experience minimal disruptions during updates. 1️⃣1️⃣ Conclusion: Blue-Green Deployments in Kubernetes redefine how we approach software updates. By introducing parallel environments, traffic-switching strategies, and robust testing, Blue-Green Deployments enable organizations to deploy updates seamlessly, minimize downtime, and embrace continuous delivery practices. #BlueGreenDeployment #ContinuousDelivery #ContinuousIntegration #CloudNative #Kubernetes

9

Master Terraform in 20 minutes || Terraform Tutorial for beginners with Document https://lnkd.in/gB5_Ykhv Terraform is a powerful Infrastructure as Code (IaC) tool used to manage and provision infrastructure resources efficiently. It allows you to define your infrastructure in a declarative way, using a human-readable configuration language called HCL (HashiCorp Configuration Language). Key Concepts Providers: These are plugins that allow Terraform to interact with different platforms like AWS, Azure, GCP, etc. Resources: These are the specific instances of infrastructure components you want to manage, such as EC2 instances, S3 buckets, or virtual networks. Modules: Reusable blocks of configuration that encapsulate infrastructure components for better organization and reusability. State: Terraform maintains a state file that records the current configuration of your infrastructure. This file is crucial for managing changes effectively. Outputs: These allow you to expose values from your infrastructure for use in other configurations or scripts. Terraform Workflow The typical Terraform workflow involves the following steps: 1) Write Configuration: Define your desired infrastructure using HCL syntax in .tf files. 2) Initialization: Run terraform init to download necessary plugins and initialize the working directory. 3) Planning: Run terraform plan to create an execution plan outlining the changes that will be made. 4) Applying: Run terraform apply to create or modify the infrastructure based on the plan. 5) Destroying: Run terraform destroy to delete all managed infrastructure resources. Terraform Tutorial for beginners with Document https://lnkd.in/gB5_Ykhv PS: Do share this post with your friends :)

367

15 Comments

Here are a few Kubernetes Certification Coupons. VALID ONLY TILL 12th November 2024. Use code "NOV24KUBECT" to save up to 47% on the Kubestronaut Bundle. Use code "ROAD2KUBECT" to save up to 40% on: -> CKA + CKS Bundle ($355 Savings) -> KCSA + CKS Exam Bundle ($348 Savings) -> KCNA + KCSA Exam Bundle ($203 Savings) -> KCNA + CKA ($348 Savings) -> CKA + CKAD + CKS ($528 Savings) I found these coupons on DevOpsCube's website. Note that the biggest sale of this year has not started yet... but if you are in a hurry you can just use these coupons... --- #kubernetes #discounts #certifications #learning

16

1 Comment

Kubernetes Offline Classes from 1st of May 6pm - 7pm Prepare for the CKA exam. #cka #offline #batch

9

One of my favorite Kubernetes thought leaders … I’ll be sure to share some of these nuggets in our upcoming FinOps+AI session on 9/6/24, (and of course, tag credit ) 😉

6