poonam khairnar

Most asked Terraform Interview Questions 1.    Why organizations are implementing DevOps? 2.    What are the Benefits of using DevOps   3.    How does Terraform differ from other infrastructure as code tools like CloudFormation or Ansible 4.    How many environments you are maintaining? 5.    Why Terraform? Why not others?   6.    Can you explain how you have used Terraform to implement infrastructure as code in a CI/CD pipeline? 7.    What is the Terraform state file, and why is it important   8.    Your team is adopting a multi cloud strategy and you need to manage resources 9.    on both AWS and Azure using terraform so how do you structure your terraform code to handle this?   10. your infrastructure contains database passwords and other sensitive information. How can you manage secrets and sensitive data in Terraform?   11. You have 20 servers created through Terraform but you want to delete one of them. Is it possible to destroy a single resource out of multiple resources using Terraform?   12. You are taskeds with migrating your existing infrastructure from terraform version 1.7 to version 1.8 so what kind of considerations and steps would you take?   13. How do you manage tfstate file in Terraform? 14. How do yo create multiple ec2 instances in terraform ? 15. AWS has released a new service, how does Terraform behave #aws #terraform #interview #cloudformation #azure

50

✅$terraform apply -target =certified 🚀Init ➡ Plan ➡ Apply ➡ HashiCorp Terraform Certified Associate ✅ Why Terraform? After spending quite some time working with Terraform, I decided it was time to get the Terraform Associate Certification by HashiCorp 💡 But what's it all about? Infrastructure as Code (IaC): Writing and managing infrastructure as code means fewer surprises and more control. Cloud-Agnostic Flexibility: Whether it's AWS, Azure, or GCP, Terraform has got you covered, making it easier to manage resources across different platforms. Version Control: Just like your code, you can version and track your infrastructure. Automation Power: Terraform automates infrastructure management, saving time and reducing errors. Seamless Collaboration: With a single source of truth for infrastructure, teams can collaborate more effectively and avoid costly misconfigurations. #Terraform #cloud #IAC #Prometeia

31

6 Comments

Hi Friends I am going to publish Kubernetes Components in simple form for better understanding . At Master Node: >Kube-api : It maintain communication into Cluster >Kube-etcd : It contain complete Cluster Information ; It save information into yaml format or we can say contain complete Backup information of Cluster . >Kube-C0ntroller : It give instruction to Worker node (Kubelet) if any request initiated by Master to worker node, Same has been acknowledge by Worker node components (Kubelet) . 4>Kube-Scheduler: It determines best fit worker node or host node to run application pod . Worker Node Components: 1>Docker: Works as Container engine 2>Kubelet : Its work as agent of Master node means which receive instruction from Master node (Controller) and provide acknowledgment to Master (Controller) . 3>Kube-Proxy: Works as Load balancer running on each Worker node (Host Node) . It distribute the traffic across all Container application which is running inside the Host .

111

5 Comments

🛠 DevOps Interview Question🌟 1. What is a statefile? 2. Where do you store the statefile? 3. What is a null resource in Terraform? 4. CI/CD workflow. 5. Terraform code to deploy an EC2 instance. 6. What will appear in the Terraform plan if you comment out a resource block in the above code? 7. Write a script to find the largest and smallest elements of an integer array. 8. Entry point vs CMD in a Dockerfile. 9. Add vs Copy in Dockerfile. 10. Describe Kubernetes architecture. 11. Do you know Ansible? 12. Difference between Secrets and ConfigMap in Kubernetes? 13. Docker lifecycle. 14. What is a ReplicaSet? 15. Is it possible to run Kubernetes in a single-node local environment? 16. How can we remove a file from Git without removing the filesystem? 17. How can we discover if a branch has already been merged in Git? 18. Application Load Balancer vs Network Load Balancer. 19. What is Route53? 20. Experience with GCP Cloud? 21. What is the difference between a single Jenkins CI/CD pipeline and multiple pipelines? 22. What are the issues of using a single pipeline vs. multiple pipelines? 23. Current Jenkins version. 24. Write a Jenkins pipeline script for Terraform deployment. 25. How to create 10 EC2 machines with incremental values like 0,1,2, etc. 26. How to terminate 9 EC2 instances and leave one EC2 machine running. 27. How to connect on-premise to an application in a VPC cloud. 28. Terraform taint. 29. Terraform refresh. 30. What will happen if someone changes resource values on the console and you do a Terraform apply? 31. What is a Terraform module, and what is its purpose? 32. What is CloudTrail? 33. What is a Load Balancer and Auto Scaling? 34. What is Databricks? #devops #linux #aws #cloud

19

2 Comments

Day 30/365 Days I have been learning Ansible in detail through Abhishek Veeramalla's YouTube playlist, which takes the viewer from beginner setup to advanced playbook usage. It has been very useful in building a solid foundation for understanding Ansible's capabilities and how it makes automation much easier. DSA - Valid Palindrome This problem may seem to be simple, but it is an excellent exercise in thinking through solutions without using any additional data structure such as stacks or lists. It refines techniques used for solving problems with a concentration on character comparison, two-pointer approaches, and edge cases in strings. Gita Learning In the Gita, Krishna teaches that one should always maintain equanimity in all situations. When things are going wrong or do not happen as expected, the only thing is to maintain balance—neither too attached to success nor too disappointed by failure. This is where true wisdom lies because, in this balanced approach, one remains focused, resilient. #Automation #Ansible #Learn #DSA #GitaWisdom #Mindfulness #GrowthJourney #ProblemSolving #pepsico #pep+

13

Hi 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐢𝐨𝐧𝐬.....!!👋 #Usecase The main causes of issues in Kubernetes today are data loss and stability problems. This example will offer suggestions on how to use EFS instead of EBS in a Kubernetes setting, as well as how to manage pod data even after it's ended. Today's discussion focuses on below points with Usecase 1) How CSI Works 2) CSI in Kubernetes 3) How to create eks envionment 4) How to EFS drive integated with eks 5) Deploy the application in EKS 6) validation of efs after terminate the pods By practicing using the use case, you can gain a deeper understanding of EFS. The Container Storage Interface (CSI) is an industry-standard API specification designed to ensure compatibility between container orchestrators (like Kubernetes) and various storage systems. Developed by the Cloud Native Computing Foundation (CNCF), CSI simplifies and unifies how containerized applications interact with storage resources, providing a consistent, flexible way for containers to access, manage, and consume storage from different vendors https://lnkd.in/gud2F6ki 𝐇𝐚𝐩𝐩𝐲 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠 😀 ✨Follow me Sreekanth Kurapati on LinkedIn for interesting information and Quick Learnings.✨ Thank you to everyone who has been part of this journey! Let's keep pushing the boundaries of what's possible in the world of DevOps together. 👩‍💻ᴛᴇᴄʜɴᴏʟᴏɢʏ ɪɴꜱᴘɪʀᴇʀꜱ👩‍💻 Sabiha Ashik | Yujun Liang ⎈ ☁️| Gineesh Madapparambath | Bhuvaneswari Subramani | Bibin Wilson | Abhishek Veeramalla 💪#aws #devops #continuouslearning #awscommunity #learing #carrier #tcs #awsdevopsengineer

41

Terraform imp commands and concepts 1. terraform init: Initializes a Terraform working directory. 2. terraform validate: Validates the Terraform configuration files. 3. terraform fmt: Formats the Terraform configuration files. Section 2: Infrastructure Management 4. terraform apply: Applies the configuration to create or update infrastructure. 5. terraform destroy: Destroys the infrastructure managed by Terraform. 6. terraform refresh: Refreshes the Terraform state to match the actual infrastructure. 7. terraform show: Shows the Terraform state and configuration. Section 3: State Management 8. terraform state list: Lists the resources in the Terraform state. 9. terraform state show: Shows the details of a specific resource in the Terraform state. 10. terraform state rm: Removes a resource from the Terraform state. 11. terraform state mv: Moves a resource from one state to another. Section 4: Module Management 12. terraform get: Downloads and installs Terraform modules. 13. terraform module: Manages Terraform modules. 14. terraform module init: Initializes a Terraform module. Section 5: Provider Management 15. terraform providers: Lists the available Terraform providers. 16. terraform provider: Manages Terraform providers. 17. terraform provider init: Initializes a Terraform provider. Section 6: Workspace Management 18. terraform workspace: Manages Terraform workspaces. 19. terraform workspace new: Creates a new Terraform workspace. 20. terraform workspace select: Selects a Terraform workspace. Section 7: Debugging and Troubleshooting 21. terraform debug: Enables debug logging for Terraform. 22. terraform logs: Shows the Terraform logs. 23. terraform console: Opens a Terraform console for interactive debugging. Section 8: Import and Export 24. terraform import: Imports existing infrastructure into Terraform. 25. terraform export: Exports the Terraform state to a file. Section 9: Miscellaneous 26. terraform version: Shows the Terraform version. 27. terraform help: Shows the Terraform help. 28. terraform upgrade: Upgrades Terraform to the latest version. Section 10: Advanced Topics 29. terraform console: Opens a Terraform console for interactive debugging. 30. terraform graph: Generates a graph of the Terraform configuration. 31. terraform output: Shows the output of a Terraform configuration. Section 11: Terraform CLI 32. terraform cli: Manages the Terraform CLI. 33. terraform cli config: Configures the Terraform CLI. Section 12: Terraform Configuration 34. terraform config: Manages the Terraform configuration. 35. terraform config init: Initializes a Terraform configuration. Section 13: Terraform State Backend 36. terraform state backend: Manages the Terraform state backend. 37. terraform state backend init: Initializes a Terraform state backend. Section 14: Terraform Workspaces 38. terraform workspace: Manages Terraform workspaces. 39. terraform workspace new: Creates a new Terraform workspace. #devops #terraform #commands

132

4 Comments

🚨 Terraform important commands and concepts 1. terraform init: Initializes a Terraform working directory. 2. terraform validate: Validates the Terraform configuration files. 3. terraform fmt: Formats the Terraform configuration files. ▶️ Section 2: Infrastructure Management 4. terraform apply: Applies the configuration to create or update infrastructure. 5. terraform destroy: Destroys the infrastructure managed by Terraform. 6. terraform refresh: Refreshes the Terraform state to match the actual infrastructure. 7. terraform show: Shows the Terraform state and configuration. ▶️ Section 3: State Management 8. terraform state list: Lists the resources in the Terraform state. 9. terraform state show: Shows the details of a specific resource in the Terraform state. 10. terraform state rm: Removes a resource from the Terraform state. 11. terraform state mv: Moves a resource from one state to another. ▶️ Section 4: Module Management 12. terraform get: Downloads and installs Terraform modules. 13. terraform module: Manages Terraform modules. 14. terraform module init: Initializes a Terraform module. ▶️ Section 5: Provider Management 15. terraform providers: Lists the available Terraform providers. 16. terraform provider: Manages Terraform providers. 17. terraform provider init: Initializes a Terraform provider. ▶️ Section 6: Workspace Management 18. terraform workspace: Manages Terraform workspaces. 19. terraform workspace new: Creates a new Terraform workspace. 20. terraform workspace select: Selects a Terraform workspace. ▶️ Section 7: Debugging and Troubleshooting 21. terraform debug: Enables debug logging for Terraform. 22. terraform logs: Shows the Terraform logs. 23. terraform console: Opens a Terraform console for interactive debugging. ▶️ Section 8: Import and Export 24. terraform import: Imports existing infrastructure into Terraform. 25. terraform export: Exports the Terraform state to a file. ▶️ Section 9: Miscellaneous 26. terraform version: Shows the Terraform version. 27. terraform help: Shows the Terraform help. 28. terraform upgrade: Upgrades Terraform to the latest version. ▶️ Section 10: Advanced Topics 29. terraform console: Opens a Terraform console for interactive debugging. 30. terraform graph: Generates a graph of the Terraform configuration. 31. terraform output: Shows the output of a Terraform configuration. ▶️ Section 11: Terraform CLI 32. terraform cli: Manages the Terraform CLI. 33. terraform cli config: Configures the Terraform CLI. ▶️ Section 12: Terraform Configuration 34. terraform config: Manages the Terraform configuration. 35. terraform config init: Initializes a Terraform configuration. ▶️ Section 13: Terraform State Backend 36. terraform state backend: Manages the Terraform state backend. 37. terraform state backend infit: Initializes a Terraform state backend. ▶️ Section 14: Terraform Workspaces 38. terraform workspace: Manages Terraform workspaces. 39. terraform workspace new: Creates a new Terraform

30

Q- Why use PVC when PV is there in Kubernetes???? Ans- PVCs are requests for those resources and also act as claim checks to the resource. So a persistent volume (PV) is the "physical" volume on the host machine that stores your persistent data. A persistent volume claim (PVC) is a request for the platform to create a PV for you, and you attach PVs to your pods via a PVC. Always remember if PVC is "x" units then PV is >="x" units. but never less... If you try to create a PVC that is more than the size of the PV, the PVC claim will fail and the pods that use the PVC will be marked "Pending". However, a PVC can bind to a bigger PV when there is no smaller available PV. Simple????!! 🤠

1

Terraform commands

1

✨ Making Strong Profile - 1 #newskilladded ⚡ CI CD pipeline using Jenkins and Ansible 🖊 What I learned: 1. Continuous Integration and Continuous Delivery (CI/CD) 2. Continuous Integration with Jenkins 3. Jenkins CLI (Command Line Interface) 4. Deployment 5. Jenkins X 6. Jenkins with Docker 7. Jenkins with Ansible 8. Managing and Monitoring Jenkins #devops #agile #skills #plm

24

1 Comment

AWS CloudWatch interview questions * *Basic Questions 1. What is Amazon CloudWatch? 2. What are the main features of CloudWatch? 3. What is a CloudWatch Metric? 4. How does CloudWatch collect data? 5. What are CloudWatch Alarms, and how are they used? 6. What is the retention policy for CloudWatch Logs? 7. What is a namespace in CloudWatch Metrics? *Intermediate Questions 8. What are CloudWatch Logs Insights, and how are they used? 9. How do you create a custom metric in CloudWatch? 10. What are CloudWatch Events, and how do they work? 11. How does CloudWatch differ from AWS CloudTrail? 12. What is the difference between basic and detailed monitoring in CloudWatch? 13. Can CloudWatch monitor on-premises servers? *Advanced Questions 14. How can CloudWatch be integrated with third-party tools? 15. How do you analyze large volumes of logs in CloudWatch efficiently? 16. What are metric filters in CloudWatch Logs? 17. Can CloudWatch trigger Auto Scaling actions? If so, how? 18. How do you optimize CloudWatch usage to reduce costs? 19. How does the CloudWatch Agent work, and what is its purpose? 20. What is the maximum number of metrics you can include in a CloudWatch dashboard? *Scenario-Based Amazon CloudWatch Questions 1. How would you monitor the CPU usage of an EC2 instance and get alerted when it exceeds a certain threshold? 2. How can you configure CloudWatch to automatically delete logs after 30 days? 3. What steps would you take to create a dashboard that shows metrics from multiple AWS services? 4. How would you monitor free disk space on an on-premises server using CloudWatch? 5. Your application logs contain both info and error logs, but you only want to monitor errors. How would you set this up in CloudWatch? 6. How can you monitor and set alerts for memory usage on an EC2 instance that is running out of memory frequently? 7. How would you trigger a Lambda function when an EC2 instance is started or stopped? 8. How can you use CloudWatch to scale resources dynamically based on high traffic during specific hours? 9. How would you monitor the number of API requests made to an S3 bucket? 10. Your CloudWatch Logs costs are increasing significantly due to high log volumes. What steps can you take to optimize costs? 11. How would you monitor and analyze the performance of containers running in an ECS cluster? 12. What steps would you take to troubleshoot delayed notifications from CloudWatch alarms? 13. How would you use CloudWatch to track the execution time of Lambda functions and get alerted for anomalies? 14. How can CloudWatch help you identify and respond to a sudden spike in read/write latency for an RDS database? 15. How would you configure CloudWatch to monitor custom metrics from your application? #AWSCloudwatch #DevOps #Interviewpreparation

47

Terraform Important Commands terraform init It initializes a working directory containing Terraform Configuration Files. It downloads required provider plugins to provision infrastructure. It will initialize terraform backend and terraform modules when we’re using backend as S3 Bucket to maintain terraform state file and terraform modules to reuse terraform configuration files. terraform validate It validates the syntax of Terraform Configuration Files. terraform fmt It can be used to format Terraform Configuration Files look clean and neat. terraform plan It can be used to create an execution plan which gives the changes that Terraform Plans to make changes to infrastructure. terraform apply -auto-approve It executes planned actions like creating, updating or deleting infrastructure resources to match the new state created as per Terraform Configuration Files. terraform destroy -auto-approve It can be used to destroy infrastructure. Resources which are created and maintained by terraform state file will be deleted. Note -auto-approve can be used with terraform apply and terraform destroy commands to avoid prompting a conformation message while provisioning and destroying infrastructure. terraform apply --var “ServerName=Jenkins” terraform apply --var “ServerName=Jenkins” --var “AvailabilityZone=ap-south-1a” We can pass value to a declared variable in Terraform Configuration Files at Runtime. Note We can also pass values to Multiple Variables. terraform apply -var-file=“production.tfvars" When we maintain defined variables and its values in a file to pass it to Terraform Configuration Files. Terraform Workspace Commands Terraform Workspaces can be used for Isolating Terraform State Files for Same Terraform Configurations.
 terraform workspace list List Terraform Workspaces Create New Terraform Workspace terraform workspace new <Workspace_Name> Switch to Workspace terraform workspace select <Workspace_Name> Delete Workspace terraform workspace delete <Workspace_Name> Terraform State Backend Commands When Terraform State Backend is Configured with S3 and whenever we make any changes in S3 backend configurations. terraform init -reconfigure -backend-config="production.tfbackend" terraform state list Displays resources provisioned using Terraform State File. terraform state show <ResourceType_ResourceName> Displays what resources are provisioned under a Particular Resource. #DevOps #Dockerfile #Maven #Java #Git #GitHub #BitBucket #Sonarqube #Nexus #Jenkins #AWS #AmazonWebServices #Azure #Docker #DockerSwarm #Kubernetes #AWSECR #Pipeline #Infrastructure #Linux #Cloud #CloudComputing #GitBranchingStrategy #BestPractices #Interview #InterviewQuestion #InterviewTip #DevOpsRoadMap #Terraform

34

Azure Kubernetes Service(AKS) Cluster upgradation steps. ********************** Pre-work upgradation---> (Backup your cluster & check compatibility ) ********************************************** 1. check the current version of your AKS cluster az aks show --resource-group <resource-group-name> --name <aks-cluster-name> --query kubernetesVersion 2. check available upgrades az aks get-upgrades --resource-group <resource-group-name> --name <aks-cluster-name> --output table 3. upgrade Control Plane az aks upgrade --resource-group <resource-group-name> --name <aks-cluster-name> --kubernetes-version <new-version> 4. After control Plane upgradation, next move to nodepool upgrade I) list all node pools az aks nodepool list --resource-group <resource-group-name> -- cluster-name <aks-cluster-name> --output table II) upgrade a node pool az aks nodepool upgrade --resource-group <resource-group-name> --cluster-name <aks-cluster-name> --name <nodepool-name> -- kubernetes-version <new-version> 5. Verify the Upgrade Kubectl get node 6. Test the Cluster Test your applications and workloads to check weather running correctly on the upgraded Kubernetes version 7. keep monitoring Cluster.

1

Job 1 - Pulling Java project code from git 1st continuos integration using Jenkins- Step  Log in with your Jenkins url- Public IP:8080 ---> Log in with your username and passwords --> Click on New Item for your project - give project name --> therer are multipule option select as per your requirment - I am selecting Freestyle project ------> Go to source code managment select git if code available on git - ---> provide the code link if it is private provide the credentials or public no need to provide credentials -----> Specify the branch name --> if you want automation - please select the Build Environment select the option as per your requirment ---> select the time * * * * * mens every minuts you can changes as per your requirment 1st * - Minuts 2* - Hours 3* days 4* Month 5* year ---> Select the buld Steap select as per your Jenkins Envoirment and write the script for code bulding Details step available in video - https://lnkd.in/decZ6mrq

6

1 Comment

If I edit my resume it will look like this - Frontend :- React,Svelte, Angular, Javascript ,css,html,Browser, Backend:- Java Springboot Microservices ,Security, Distributed system,distributed transaction , JPA,Spring security, Saga, kafka Devops :- Docker Jenkins Rancher Kubernates Database: Postgresql Dynamodb Language : Javascript in depth Java DSA and System Design

2

Jenkins Jobs as a code / Pipeline Stages Multi-configuration project Multibranch Pipeline Jenkins Schedule Aliases Jenkins Views & Folders

9