<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Varsha Salve on Medium]]></title>
        <description><![CDATA[Stories by Varsha Salve on Medium]]></description>
        <link>https://medium.com/@varshasalve102?source=rss-a27230c36664------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*rAqmwjctDbrknJqHn6uqCA.jpeg</url>
            <title>Stories by Varsha Salve on Medium</title>
            <link>https://medium.com/@varshasalve102?source=rss-a27230c36664------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:15:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@varshasalve102/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Networking for DevOps Engineers — A Must-Know Guide! ]]></title>
            <link>https://medium.com/@varshasalve102/networking-for-devops-engineers-a-must-know-guide-1c36ee0d6d88?source=rss-a27230c36664------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c36ee0d6d88</guid>
            <dc:creator><![CDATA[Varsha Salve]]></dc:creator>
            <pubDate>Fri, 20 Jun 2025 05:44:48 GMT</pubDate>
            <atom:updated>2025-06-20T05:44:48.643Z</atom:updated>
            <content:encoded><![CDATA[<h3>Networking for DevOps Engineers — A Must-Know Guide! 🧠</h3><p>Most DevOps roles expect us to know how networks work, but few of us come from a networking background. So here’s a quick, real-world-friendly guide to the networking fundamentals every DevOps/SRE/cloud engineer should actually understand:<br>OSI Model (The 7-layer cake of communication)<br> From cables to apps — understanding where things break (and why).<br>TCP vs UDP<br>TCP: Like a reliable courier (signs receipts, tracks delivery).<br>UDP: Like a fast food order (no tracking, hope it arrives!).<br> Used in everything from Kubernetes to webhooks.<br>IP, Subnetting, and Routing<br>Ever wonder how pods talk across clusters or how your EC2 finds a database?<br>This is the magic behind it.<br>DNS &amp; Ports<br>53 = DNS, 22 = SSH, 443 = HTTPS<br>If you’ve ever set up NGINX or exposed a service, you’ve dealt with these.<br>VPNs<br> Secure tunnels for remote DevOps engineers. Encrypt everything.<br> Used for private cloud access, secure maintenance, or bypassing nasty public endpoints.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c36ee0d6d88" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Interview Questions for Cloud & DevOps Engineer Role]]></title>
            <link>https://medium.com/@varshasalve102/interview-questions-for-cloud-devops-engineer-role-a02f63d914bb?source=rss-a27230c36664------2</link>
            <guid isPermaLink="false">https://medium.com/p/a02f63d914bb</guid>
            <dc:creator><![CDATA[Varsha Salve]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 09:54:29 GMT</pubDate>
            <atom:updated>2025-06-19T09:54:29.208Z</atom:updated>
            <content:encoded><![CDATA[<p>💎 Level 1 -<br>1. cicd workflow, what kind of pipeline.<br>2. use of webhook<br>3. purpose of webhook<br>4. stages of pipeline…<br>5. shared libraries in jenkins?<br>6. how do we define shared libraries?<br>7. how are shared libraries written?<br>8. how do you define a pipeline and call it?<br>9. what kind of app you deploy on the pipeline?<br>10. basic structure, folder structure of helm?<br>11. what command are you using deployment in helm<br>12. in the Jenkins pipeline, the pipeline is running successfully but the build is not happening, what are the issues?<br>13. in kubernetes, what are the errors you are getting, why they come and how you resolve?<br>14. explain the crash loop back off,<br>15. image pull error?<br>16. command to go inside a pod?<br>17. how can you create the kubernetes class?<br>18. what are the steps to create the cluster?<br>19. what is the master node and other node?<br>20. code to create a cluster using terraform?<br>21. stages in docker images?<br>22. DB entry point, CMD <br>23. why do we use entrypoint, CMD<br>24. DB ec2, eks, ecs<br>25. command to connect ecs<br>26. which tool are you using for deployment?<br>27. which registry for storing the docker images?</p><p>💎 Level 2 -<br>1. Branching strategy?<br>2. your release branch will break, then how u will avoid this kind of issues, then how do you merge?<br>3. in production having some bugs, how will you resolve?<br>4. typical deployment flow?<br>5. cicd workflow?<br>6. how do we do a full quality check?<br>7. jenkins file, different stages…<br>8. shared libraries in jenkins file?<br>9. typical structure of shared libraries…<br>10. are you aware of security scanning tools?<br>11. how do you pass the environment variables on docker build command.<br>12. what services do you use for storing the images?<br>13. DB, how do you establish the connection?<br>14. how do you scan the images at the registry level?<br>15. any extension you are using for image scanning?<br>16. authentication of eks cluster?<br>17. storing the secrets?<br>18. how to create lambda function, how it’s taking the artifacts.<br>19. options on lambda to push the artifacts?<br>20. what is email signing and helm chart signing?<br>21. which tool for signing the helm chart?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a02f63d914bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top DevOps Certifications (2025)]]></title>
            <link>https://medium.com/@varshasalve102/top-devops-certifications-2025-9b73532b9bdf?source=rss-a27230c36664------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b73532b9bdf</guid>
            <dc:creator><![CDATA[Varsha Salve]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 09:30:54 GMT</pubDate>
            <atom:updated>2025-06-19T09:30:54.157Z</atom:updated>
            <content:encoded><![CDATA[<p>1. AWS Certified DevOps Engineer — Professional<br> • Best for: Engineers working with AWS.<br> • Covers: CI/CD, automation, monitoring, logging, and security in AWS.<br> • Prerequisite: AWS Certified Developer or SysOps Admin (recommended).<br> • Why it’s great: High industry demand and directly tied to AWS ecosystem.</p><p>2. Certified Kubernetes Administrator (CKA)<br> • Best for: Container orchestration and Kubernetes.<br> • Covers: Cluster architecture, networking, deployments, troubleshooting.<br> • Why it’s great: Kubernetes is a core DevOps technology. CKA proves strong hands-on skills.</p><p>3. HashiCorp Certified: Terraform Associate<br> • Best for: Infrastructure as Code (IaC) with Terraform.<br> • Covers: Terraform basics, modules, state, lifecycle, and CLI usage.<br> • Why it’s great: Terraform is a leading IaC tool used across cloud platforms.</p><p>4. Docker Certified Associate (DCA)<br> • Best for: Containerization and Docker fundamentals.<br> • Covers: Docker CLI, images, networking, volumes, orchestration.<br> • Why it’s great: Validates container skills that are foundational to DevOps.</p><p>5. Microsoft Certified: DevOps Engineer Expert (Azure)<br> • Best for: Engineers working in Azure environments.<br> • Covers: Azure DevOps, CI/CD pipelines, infrastructure, testing, monitoring.<br> • Why it’s great: Valuable if you’re in an Azure-heavy environment.</p><p>6. Google Professional DevOps Engineer<br> • Best for: GCP-focused engineers.<br> • Covers: Service reliability, CI/CD, SRE principles, security, compliance.<br> • Why it’s great: Strong cloud-native DevOps focus with SRE angle.</p><p>7. Red Hat Certified Engineer (RHCE)<br> • Best for: Linux admins transitioning to DevOps.<br> • Covers: Linux automation with Ansible, system administration, scripting.<br> • Why it’s great: Strong foundation in automation and system management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*T0CnLO-I5ONoxY9XiTnahw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b73532b9bdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps engineer, here’s a roadmap]]></title>
            <link>https://medium.com/@varshasalve102/devops-engineer-heres-a-roadmap-30497abbb7dc?source=rss-a27230c36664------2</link>
            <guid isPermaLink="false">https://medium.com/p/30497abbb7dc</guid>
            <dc:creator><![CDATA[Varsha Salve]]></dc:creator>
            <pubDate>Mon, 19 May 2025 05:07:44 GMT</pubDate>
            <atom:updated>2025-05-19T05:07:44.308Z</atom:updated>
            <content:encoded><![CDATA[<ol><li>𝗟𝗶𝗻𝘂𝘅 𝗢𝗦<br> Learn the fundamentals of the Linux operating system, such as the file system, shell commands, and basic system administration.<br> Practice using Linux in a virtual machine or on a cloud platform.<br> <br> 2. 𝗦𝗰𝗿𝗶𝗽𝘁𝗶𝗻𝗴<br> Learn a scripting language such as Python or Go.<br> Learn how to automate common tasks with scripting.<br> <br> 3. 𝗡𝗲𝘁𝘄𝗼𝗿𝗸𝗶𝗻𝗴<br> Learn the basics of networking, such as TCP/IP, DNS, and HTTPS.<br> Understand how to troubleshoot network problems.<br> <br> 4. 𝗚𝗜𝗧<br> Learn how to use GIT for version control.<br> Learn how to collaborate with others using GIT.<br> <br> 5. 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀<br> Learn about containerization and Docker.<br> Learn how to build, deploy, and manage Docker containers.<br> <br> 6. 𝗖𝗹𝗼𝘂𝗱<br> Learn about the major cloud platforms, such as AWS, GCP, and Azure.<br> Learn how to use cloud services to build and deploy applications.<br> <br> 7. 𝗖𝗜/𝗖𝗗<br> Learn about continuous integration and continuous delivery (CI/CD).<br> Learn how to use CI/CD tools to automate the software development and delivery process.<br> <br> 8. 𝗢𝗿𝗰𝗵𝗲𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻<br> Learn about container orchestration and Kubernetes.<br> Learn how to use Kubernetes to manage and scale containerized applications.<br> <br> 9. 𝗢𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗶𝗹𝗶𝘁𝘆<br> Learn about observability and monitoring.<br> Learn how to use monitoring tools to collect and analyze metrics, logs, and traces.<br> Infrastructure as Code<br> <br>10. 𝗟𝗲𝗮𝗿𝗻 𝗮𝗯𝗼𝘂𝘁 𝗶𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗮𝘀 𝗰𝗼𝗱𝗲 (𝗜𝗮𝗖).<br> Learn how to use IaC tools to automate the provisioning and configuration of infrastructure.<br> <br>11. 𝗣𝗼𝗹𝗶𝗰𝘆<br> Learn about policy as code and tools like OPA and Kyverno.<br> Understand how to use policy to enforce compliance and security.<br> <br>12. 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 𝗠𝗲𝘀𝗵<br> Learn about service meshes and Istio.<br> Understand how to use service meshes to manage traffic between microservices.<br> <br>13. 𝗖𝗵𝗮𝗼𝘀 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴<br> Learn about chaos engineering and tools like Chaos Mesh and Litmus.<br> Understand how to use chaos engineering to improve the resilience of your systems.<br> <br>14. 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲<br> Once you have a solid foundation in the above topics, you need to gain experience in DevOps. You can do this by working on personal projects, contributing to open source projects, or getting a job as a DevOps engineer.<br> <br>15. 𝗖𝗲𝗿𝘁𝗶𝗳𝗶𝗰𝗮𝘁𝗶𝗼𝗻<br> Getting certified in DevOps can also be helpful for your career. There are a number of different DevOps certifications available, such as the AWS Certified DevOps Engineer</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WpoYv5SnkmdQzWfBD1pXMw.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30497abbb7dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Big News for Terraform Users! ]]></title>
            <link>https://medium.com/@varshasalve102/big-news-for-terraform-users-bf8c49f2e6a8?source=rss-a27230c36664------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf8c49f2e6a8</guid>
            <dc:creator><![CDATA[Varsha Salve]]></dc:creator>
            <pubDate>Mon, 19 May 2025 05:01:15 GMT</pubDate>
            <atom:updated>2025-05-19T05:01:15.009Z</atom:updated>
            <content:encoded><![CDATA[<p>Terraform has just made state management way simpler — S3 native state locking is now fully supported! 🙌 That means no more DynamoDB tables just for state locking. Less complexity, fewer resources to manage, and a cleaner backend configuration.</p><p>What’s Changing?</p><p>Before, you had to use a DynamoDB table to handle state locks:</p><p>terraform {<br> backend “s3” {<br> bucket = “your-terraform-state-bucket”<br> key = “path/to/your/statefile.tfstate”<br> region = “us-east-1”<br> dynamodb_table = “your-dynamodb-lock-table” # Extra overhead<br> encrypt = true<br> }<br>}</p><p>Now, with S3 native locking, all you need is:</p><p>terraform {<br> backend “s3” {<br> bucket = “your-terraform-state-bucket”<br> key = “path/to/your/statefile.tfstate”<br> region = “us-east-1”<br> encrypt = true<br> lock_enabled = true # Simple &amp; built-in!<br> }<br>}</p><p>Why This Matters?<br> • Less setup — No more managing DynamoDB for locks<br> • Fewer dependencies — Keep things lightweight<br> • Seamless transition — Just update your backend config</p><p>If you’re using Terraform, now’s the time to test this in your dev environment before DynamoDB locking gets deprecated. ⏳</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf8c49f2e6a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Terraform Just Got Simpler! ✨]]></title>
            <link>https://medium.com/@varshasalve102/terraform-just-got-simpler-19b099dd722c?source=rss-a27230c36664------2</link>
            <guid isPermaLink="false">https://medium.com/p/19b099dd722c</guid>
            <category><![CDATA[terraform]]></category>
            <dc:creator><![CDATA[Varsha Salve]]></dc:creator>
            <pubDate>Mon, 19 May 2025 04:57:40 GMT</pubDate>
            <atom:updated>2025-05-19T04:57:40.196Z</atom:updated>
            <content:encoded><![CDATA[<p>If you’re still using S3 + DynamoDB to manage Terraform state… here’s your sign to upgrade your workflow</p><p>With recent versions of Terraform (v1.10+) you no longer need a separate DynamoDB table for state locking.</p><p>Yes, you read that right. Terraform now supports native state locking within S3 buckets!<br>Less infra, less complexity, same safety ✅</p><p>What this means for you:<br> • 🧼 Clean backend configs<br> • 🔐 Built-in state locking<br> • ⚙️ Fewer moving parts to manage<br> • ⏱️ Faster bootstraps for new environments<br> <br>To enable it, just set the new argument use_lockfile to true in the s3 backend block.</p><p>terraform {<br> backend “s3” {<br> bucket = “mybucket”<br> key = “path/to/my/key”<br> region = “us-east-1”<br> use_lockfile = true<br> }<br>}</p><p>This is a huge win for anyone working with IaC at scale on AWS.<br>If you’re building your backends the old way, it might be time to modernize!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Q8pSxYytRyWzURTWpfLkBg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19b099dd722c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is DevOps?]]></title>
            <link>https://medium.com/@varshasalve102/what-is-devops-71014695c1bb?source=rss-a27230c36664------2</link>
            <guid isPermaLink="false">https://medium.com/p/71014695c1bb</guid>
            <dc:creator><![CDATA[Varsha Salve]]></dc:creator>
            <pubDate>Sat, 17 May 2025 09:44:46 GMT</pubDate>
            <atom:updated>2025-05-17T09:44:46.567Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>DevOps</strong> is a combination of development (Dev) and operations (Ops) practices that aim to shorten the software development lifecycle and deliver high-quality software continuously. It’s not just a set of tools or a methodology, but rather a culture that emphasizes collaboration, automation, and integration between software developers and IT operations teams.</p><p>In simpler terms, <strong>DevOps</strong> integrates the people, processes, and technologies involved in the software development and IT operations lifecycle. This enables teams to collaborate more effectively, work faster, and deliver better products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fPDmBkQVOqsU78XwO6j3gA.png" /></figure><p>Key Principles of DevOps:</p><ol><li><strong>Collaboration</strong>: Encourages better communication between development teams (who write the code) and operations teams (who deploy and maintain the software in production).</li><li><strong>Automation</strong>: Automates repetitive tasks (e.g., testing, deployment, infrastructure setup) to speed up the process and reduce human error.</li><li><strong>Continuous Integration (CI)</strong>: Developers frequently integrate code into a shared repository, where it is automatically tested and validated to detect issues early.</li><li><strong>Continuous Delivery (CD)</strong>: Code is continuously delivered to production environments after passing automated tests, ensuring fast and reliable deployment.</li><li><strong>Monitoring and Feedback</strong>: Teams monitor applications in real-time to catch issues early, and provide feedback loops to improve performance and functionality.</li></ol><h3><strong>Why Do We Use DevOps in Industries?</strong></h3><p><strong>1. Faster Time to Market:</strong></p><ul><li>DevOps accelerates the software development lifecycle by enabling continuous integration and delivery. This means software features, bug fixes, and updates are deployed more frequently, allowing businesses to release products faster and respond to market needs more quickly.</li></ul><p><strong>2. Improved Collaboration and Communication:</strong></p><ul><li>By fostering a culture of collaboration between developers and operations teams, DevOps breaks down traditional silos. The result is a more efficient workflow where everyone works toward common goals, improving communication and reducing misalignments.</li></ul><p><strong>3. Better Quality and Reliability:</strong></p><ul><li>Automation and continuous testing help catch bugs and issues earlier in the development process, reducing the chances of issues reaching production. This leads to more stable and reliable software.</li><li><strong>Monitoring and feedback loops</strong> in DevOps allow teams to detect and address issues quickly in production environments.</li></ul><p><strong>4. Scalability and Flexibility:</strong></p><ul><li>DevOps practices are designed to handle large-scale software deployments. Through automation, infrastructure as code, and cloud technologies, teams can scale their applications and environments up or down as needed.</li><li>DevOps enables the ability to roll out changes quickly and easily, adapt to user demands, and deploy to various environments seamlessly (e.g., development, staging, production).</li></ul><p><strong>5. Continuous Improvement:</strong></p><ul><li>DevOps is inherently designed to encourage continuous feedback and improvement. With regular monitoring and data analysis, teams can quickly identify areas that need optimization, leading to incremental improvements over time.</li><li><strong>Automated testing</strong> and <strong>CI/CD pipelines</strong> ensure that software is tested constantly, reducing the chances of bugs or defects slipping through the cracks.</li></ul><p><strong>6. Cost Efficiency:</strong></p><ul><li>By automating repetitive tasks, reducing errors, and optimizing workflows, DevOps helps cut operational costs.</li><li>Additionally, it eliminates the need for extensive manual testing or system maintenance, making the overall development and operational costs lower.</li></ul><p><strong>7. Enhanced Security:</strong></p><ul><li>DevOps incorporates <strong>security practices</strong> through a concept called <strong>DevSecOps</strong>, which integrates security testing and vulnerability scanning into the CI/CD pipeline.</li><li>Continuous monitoring also helps detect and respond to security threats in real-time, ensuring a more secure software lifecycle.</li></ul><p><strong>8. Increased Innovation:</strong></p><ul><li>Because DevOps focuses on automation and efficiency, developers can focus more on writing code and experimenting with new features. This fosters innovation since developers spend less time on manual tasks (like deployment) and more on delivering creative solutions.</li></ul><p><strong>9. Reduced Downtime and Faster Recovery:</strong></p><ul><li>By automating deployments and using consistent configurations, DevOps helps reduce downtime during releases or updates.</li><li>If an issue arises, quick rollbacks and automated disaster recovery mechanisms ensure minimal service disruption.</li></ul><h3><strong>How Do Companies Use DevOps in Their Operations?</strong></h3><p><strong>Automating Software Delivery:</strong></p><ul><li><strong>CI/CD pipelines</strong> are implemented to automate the process of code integration, testing, and deployment. Developers commit code to a repository, which automatically triggers tests, builds, and deployments to production environments.</li></ul><p><strong>2. Managing Infrastructure as Code (IaC):</strong></p><ul><li>DevOps teams use <strong>Infrastructure as Code</strong> tools like <strong>Terraform</strong>, <strong>Ansible</strong>, <strong>Puppet</strong>, or <strong>Chef</strong> to manage server provisioning, scaling, and configurations. This approach ensures consistency and reduces human error.</li></ul><p><strong>3. Monitoring and Performance Management:</strong></p><ul><li>Tools like <strong>Prometheus</strong>, <strong>Grafana</strong>, <strong>New Relic</strong>, and <strong>Datadog</strong> help track application performance, infrastructure health, and user behavior in real-time, allowing teams to quickly resolve issues before they affect customers.</li></ul><p><strong>4. Cloud Adoption and Microservices:</strong></p><ul><li>Cloud providers like <strong>AWS</strong>, <strong>Azure</strong>, and <strong>Google Cloud</strong> play a big role in DevOps, offering scalable infrastructure and managed services that support continuous deployment and integration.</li><li>Many companies also adopt <strong>microservices</strong> architecture, which aligns well with DevOps, allowing teams to deploy smaller, more manageable components of the application independently.</li></ul><p><strong>5. Collaboration Tools:</strong></p><ul><li><strong>Slack</strong>, <strong>Jira</strong>, and <strong>Trello</strong> help facilitate communication among cross-functional teams. Tools like <strong>GitHub</strong> and <strong>GitLab</strong> are commonly used for version control and code collaboration.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71014695c1bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>