<?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 Chetan Rakhra on Medium]]></title>
        <description><![CDATA[Stories by Chetan Rakhra on Medium]]></description>
        <link>https://medium.com/@chetxn?source=rss-9609085c0266------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TBGdjanzwO77zGD-DXqroQ.png</url>
            <title>Stories by Chetan Rakhra on Medium</title>
            <link>https://medium.com/@chetxn?source=rss-9609085c0266------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:45:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chetxn/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[Top 15 AWS services commonly used in DevOps♾️]]></title>
            <link>https://medium.com/@chetxn/top-15-aws-services-commonly-used-in-devops-%EF%B8%8F-5bdb6f680ff9?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bdb6f680ff9</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Tue, 01 Aug 2023 13:00:24 GMT</pubDate>
            <atom:updated>2023-08-01T13:00:24.371Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*-7PkadZyH-ZFmwUv3Tq9uw.png" /></figure><p>Top🔝 15 AWS☁️ services commonly used in DevOps♾️ are:</p><p>1. Amazon EC2💻 (Elastic Compute Cloud): Provides resizable compute capacity in the cloud.</p><p>2. Amazon S3🪣 (Simple Storage Service): Object storage service for storing and retrieving any amount of data at any time.</p><p>3. AWS Lambda📦 : A serverless, event-driven compute service that lets you run code for virtually any type of application or backend service without provisioning or managing servers.</p><p>4. Amazon RDS💾 (Relational Database Service): Manages relational databases, including Amazon Aurora, PostgreSQL, MySQL, and more.</p><p>5. Amazon CloudFormation🏗️: Provides templates to describe and provision AWS resources.</p><p>6. AWS Elastic Beanstalk🫘: Deploys, manages, and scales applications without the need to manage the infrastructure.</p><p>7. AWS CodePipeline♾️: Automates the build, test, and deployment phases of the release process.</p><p>8. AWS CodeDeploy♾️: Automates application deployments to Amazon EC2 instances, on-premises instances, or serverless Lambda functions.</p><p>9. AWS CodeCommit♾️: Hosts secure, scalable, and managed Git repositories.</p><p>10. Amazon CloudWatch👀: Monitors AWS resources and applications, providing data and actionable insights.</p><p>11. AWS Identity and Access Management🔐 (IAM): Manages access to AWS services and resources securely.</p><p>12. Amazon VPC☁️ (Virtual Private Cloud): Provides logically isolated virtual networks in the AWS cloud.</p><p>13. AWS CloudTrail🧭: Records and monitors AWS API activity, allowing governance, compliance, and operational auditing.</p><p>14. AWS Systems Manager🌍: Automates the management of AWS resources at scale.</p><p>15. AWS Elastic Load Balancing⚖️: Automatically distributes incoming application traffic across multiple targets.</p><p>🚀 Follow for more DevOps content, tips and tricks, and Hands-On Project Implementation.</p><p>GitHub Link: <a href="https://github.com/chxtan">https://github.com/chxtan</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bdb6f680ff9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The most common Docker  Terms:]]></title>
            <link>https://medium.com/@chetxn/the-most-common-docker-terms-72386c357852?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/72386c357852</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Sat, 29 Jul 2023 11:00:28 GMT</pubDate>
            <atom:updated>2023-07-29T11:00:28.832Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*md19JHjPXqqYipFf5XmpOA.gif" /></figure><p>The most common Docker 🐳 Terms:</p><p>Docker is an open-source platform that enables developers to automate the deployment, scaling, and management of applications within portable and lightweight containers.</p><p>🐳 Container: A lightweight, standalone executable software package that includes everything needed to run a piece of software, including the code, runtime, libraries, and dependencies.</p><p>🐳 Image: A read-only template used to create containers. It contains the application code, runtime, libraries, environment variables, and configurations.</p><p>🐳 Containerization: The process of creating, deploying, and running containers using technologies like Docker.</p><p>🐳 Dockerfile: A text file that contains instructions for building a Docker image.</p><p>🐳 Registry: A centralized location for storing and distributing Docker images, such as Docker Hub.</p><p>🐳 Docker Hub: A public repository where Docker images can be shared and accessed by the community.</p><p>🐳 Volume: A way to persist data in Docker containers beyond the container’s lifecycle.</p><p>🐳 Docker Compose: A tool for defining and running multi-container Docker applications using a YAML file.</p><p>🐳 Kubernetes: An open-source container orchestration platform for automating the deployment, scaling, and management of containerized applications.</p><p>🐳 Swarm: Docker Swarm is a native clustering and orchestration solution for Docker, used to manage a cluster of Docker nodes.</p><p>🐳 Service: A definition for the desired state of a container, typically used in Docker Swarm.</p><p>🐳 Container Networking: The process of enabling communication between containers and other network endpoints.</p><p>🐳 Port Mapping: The process of mapping network ports between the host and the container.</p><p>🐳 Docker Engine: The core component of Docker is responsible for running containers on a host.</p><p>These are some of the important terms in Docker, there are more terms that can be used to build and deploy containers.</p><p>🚀 Follow for more DevOps content, tips and tricks, and Hands-On Project Implementation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72386c357852" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 15 DevOps tools and their links]]></title>
            <link>https://medium.com/@chetxn/top-15-devops-tools-and-their-links-38beda094fd0?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/38beda094fd0</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[monitoring]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Wed, 26 Jul 2023 12:32:46 GMT</pubDate>
            <atom:updated>2023-07-26T12:32:46.556Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are top 15 DevOps tools and their links:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*1pA96Ot8WpyVi_fowrYCCQ.gif" /></figure><p>✅ Jenkins — Continuous Integration and Continuous Deployment Automation<br>Website: <a href="https://www.jenkins.io/">https://www.jenkins.io/</a></p><p>✅ GitHub — Version control platform and CI/CD integration<br>Website: <a href="https://github.com/">https://github.com/</a></p><p>✅ Ansible — IT automation tool for configuration management and application deployment<br>Website: <a href="https://www.ansible.com/">https://www.ansible.com/</a></p><p>✅ Puppet — Configuration management and infrastructure automation tool<br>Website: <a href="https://puppet.com/">https://puppet.com/</a></p><p>✅ Docker — Containerization platform for building, shipping, and running applications<br>Website: <a href="https://www.docker.com/">https://www.docker.com/</a></p><p>✅ Kubernetes — Container orchestration platform for automating deployment, scaling, and management of applications<br>Website: <a href="https://kubernetes.io/">https://kubernetes.io/</a></p><p>✅ Nagios — Monitoring and alerting tool for IT infrastructure<br>Website: <a href="https://www.nagios.org/">https://www.nagios.org/</a></p><p>✅ Grafana — Open-source analytics and monitoring platform<br>Website: <a href="https://grafana.com/">https://grafana.com/</a></p><p>✅ Prometheus — Monitoring and alerting toolkit<br>Website: <a href="https://prometheus.io/">https://prometheus.io/</a></p><p>✅ Terraform — Infrastructure as Code tool for managing cloud resources<br>Website: <a href="https://www.terraform.io/">https://www.terraform.io/</a></p><p>✅ SonarQube — Code quality and security analysis tool<br>Website: <a href="https://www.sonarqube.org/">https://www.sonarqube.org/</a></p><p>✅ Jira — Issue and project tracking software by Atlassian<br>Website: <a href="https://lnkd.in/d2NpUjND">https://lnkd.in/d2NpUjND</a></p><p>✅ Octopus Deploy — Automated deployment and release management tool<br>Website: <a href="https://octopus.com/">https://octopus.com/</a></p><p>✅ CircleCI — CI/CD platform for automating software builds and tests<br>Website: <a href="https://circleci.com/">https://circleci.com/</a></p><p>✅ Chef — Infrastructure automation framework<br>Website: <a href="https://www.chef.io/">https://www.chef.io/</a></p><p>🚀 Follow for more DevOps content, tips and tricks, and Hands-On Project Implementation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38beda094fd0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 10 Skills/Tools for DevOps.]]></title>
            <link>https://medium.com/@chetxn/top-10-skills-tools-for-devops-b689380af4d2?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/b689380af4d2</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Sun, 23 Jul 2023 12:08:54 GMT</pubDate>
            <atom:updated>2023-07-23T12:08:54.108Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are top 🔟 mandatory skills required if you want to become a DevOps Engineer:</p><p>I received a lot of texts, daily on LinkedIn that<br>✅ How one should start studying DevOps of his own.<br>✅ Which tools/skills are important to learn.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FKJ97XPluvkz3JLTXLjyEw.png" /></figure><p>So, here I have listed down below:</p><p>1️⃣ Operating System (Linux): A DevOps Engineer should have a strong understanding of the Linux operating system since many DevOps tools and platforms are Linux-based.</p><p>2️⃣ Automation and Scripting: Proficiency in scripting languages like Python, Bash, or Ruby is essential for automating tasks and managing infrastructure as code.</p><p>3️⃣ Continuous Integration/Continuous Deployment (CI/CD): CI/CD focuses on automating the integration and deployment of code changes. One must understand the principles of CI/CD and be proficient in using tools like Jenkins, GitLab CI/CD, or CircleCI to build, test, and deploy applications quickly and reliably.</p><p>4️⃣ Version Control Systems: As a DevOps Engineer, you should have a good understanding of version control systems, for this we mostly use Git. You’ll need to understand branching strategies, resolving merge conflicts, and track changes in code repositories.</p><p>5️⃣ Cloud Platforms: Expertise in one or more cloud platforms like AWS, Azure, or GCP is must, as cloud services are often used for scalable and flexible infrastructure.</p><p>6️⃣ Containerization: Understanding containerization technologies like Docker and container orchestration tools like Kubernetes is critical for managing and deploying applications.</p><p>7️⃣ Infrastructure as Code (IaC): Proficiency in tools like Terraform or CloudFormation is essential for provisioning and managing infrastructure resources programmatically.</p><p>8️⃣ Monitoring and Logging: DevOps Engineers should be familiar with monitoring tools like Prometheus and Grafana for collecting metrics and setting up alerts. Additionally, knowledge of logging tools like ELK (Elasticsearch, Logstash, Kibana) helps in analyzing and troubleshooting issues in real-time.</p><p>9️⃣ Security Practices: Understanding security best practices, such as securing pipelines, managing secrets, and implementing role-based access controls, is crucial to maintaining a secure DevOps environment.</p><p>🔟 Collaboration and Communication: Soft skills, including effective communication, collaboration, and problem-solving, are essential for working in a DevOps culture where cross-functional teams collaborate closely.</p><p>🚀 Follow for more DevOps content, tips and tricks, and Hands-On Project Implementation.</p><p><a href="https://www.linkedin.com/feed/hashtag/?keywords=devops&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#DevOps</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=continuousintegration&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#ContinuousIntegration</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=continuousdelivery&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#ContinuousDelivery</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=continuousdeployment&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#ContinuousDeployment</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=agile&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Agile</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=infrastructureascode&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#InfrastructureAsCode</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=automation&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Automation</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=cloudcomputing&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#CloudComputing</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=microservices&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Microservices</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=containerization&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Containerization</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=kubernetes&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Kubernetes</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=docker&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Docker</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=ansible&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Ansible</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=jenkins&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Jenkins</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=git&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Git</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=devsecops&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#DevSecOps</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=sitereliabilityengineering&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#SiteReliabilityEngineering</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=monitoring&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Monitoring</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=logging&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Logging</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=testing&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Testing</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=configurationmanagement&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#ConfigurationManagement</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=orchestration&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Orchestration</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=releasemanagement&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#ReleaseManagement</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=itil&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#ITIL</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=lean&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Lean</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=scrum&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Scrum</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=devopsculture&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#DevOpsCulture</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=collaboration&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#Collaboration</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=cicd&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#CICD</a> <a href="https://www.linkedin.com/feed/hashtag/?keywords=devopsproject&amp;highlightedUpdateUrns=urn%3Ali%3Aactivity%3A7088850639639707648">#devopsproject</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b689380af4d2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps Case Study: 5 (UPI )]]></title>
            <link>https://medium.com/@chetxn/devops-case-study-5-upi-88cc22411373?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/88cc22411373</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Thu, 29 Jun 2023 13:42:19 GMT</pubDate>
            <atom:updated>2023-06-29T13:42:19.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*Me-5IXP-7UgVf9h3KMRtcA.png" /></figure><p>UPI — Unified Payment Interface (UPI) is a real-time payment system developed by the National Payments Corporation of India (NPCI). It enables users to link their multiple bank accounts to a single mobile application and make cashless transactions between these accounts. UPI acts as a platform for instant money transfers, bill payments, and other financial transactions directly from a user’s mobile device.</p><p>Some of them are -<br><a href="https://www.linkedin.com/company/google-pay/">Google Pay</a><br><a href="https://www.linkedin.com/company/paytm/">Paytm</a><br><a href="https://www.linkedin.com/company/phonepe-internet/">PhonePe</a></p><p>DevOps, on the other hand, is a set of practices that combines software development (Dev) and operations (Ops) to enhance collaboration, automate processes, and deliver software applications more efficiently. There are some ways in which UPI can be integrated with DevOps terminology:</p><p>📌 Continuous Integration and Deployment: UPI transactions can be integrated into a CI/CD pipeline, allowing automated testing and deployment of payment-related features within applications. This ensures that the payment functionality is thoroughly tested and seamlessly deployed alongside other application updates.</p><p>📌 Infrastructure as Code (IaC): When integrating UPI with DevOps, the payment system infrastructure, such as servers, databases, and network configurations, can be managed as code using tools like Terraform or AWS CloudFormation. This enables version control, reproducibility, and easier infrastructure management in the context of UPI integration.</p><p>📌 Monitoring and Alerting: UPI integration requires monitoring transaction flows, payment gateway status, and other metrics. DevOps tools like Prometheus, Grafana, or ELK (Elasticsearch, Logstash, Kibana) can be used to collect, analyze, and visualize UPI-related metrics, allowing teams to set up alerts and respond promptly to any issues.</p><p>📌 Security and Compliance: DevOps teams can incorporate security testing, vulnerability scanning, and compliance checks into their pipelines to ensure UPI transactions are secure and compliant.</p><p>📌 Automated Testing: UPI integration can benefit from automated testing frameworks and tools to simulate various payment scenarios, validate transaction flows, and perform end-to-end testing.</p><p>This way UPI enhanced the efficiency, reliability, and security of their payment systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88cc22411373" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps Interview Series — 2(Docker)]]></title>
            <link>https://medium.com/@chetxn/devops-interview-series-2-docker-38c5eba8b99c?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/38c5eba8b99c</guid>
            <category><![CDATA[swarm]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[projects]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Wed, 21 Jun 2023 15:06:21 GMT</pubDate>
            <atom:updated>2023-06-21T15:06:21.806Z</atom:updated>
            <content:encoded><![CDATA[<h3>DevOps Interview Series — 2(Docker)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*X0fQXvDTvxK0CMhW" /></figure><ol><li>What is Docker?</li></ol><p>Docker is an open-source platform that allows you to automate the deployment, scaling, and management of applications using containerization.</p><p>2. What is a container?</p><p>A container is a lightweight and isolated environment that encapsulates an application and its dependencies, allowing it to run consistently across different environments.</p><p>3. How is Docker different from virtualization?</p><p>Virtualization emulates an entire operating system, while Docker containers share the host system’s kernel and only isolate the application processes.</p><p>4. What is Docker image?</p><p>A Docker image is a read-only template that contains the application and all its dependencies. It is used to create Docker containers.</p><p>5. How do you create a Docker image?</p><p>You can create a Docker image using a Dockerfile, which is a text file that contains a set of instructions for building the image.</p><p>6. What is a Dockerfile?</p><p>A Dockerfile is a text file that contains instructions for building a Docker image. It specifies the base image, application code, dependencies, and other configurations.</p><p>7. What is Docker Compose?</p><p>Docker Compose is a tool that allows you to define and manage multi-container Docker applications. It uses a YAML file to configure the application’s services and their dependencies.</p><p>8. How do you link containers in Docker?</p><p>In Docker, you can link containers using the — link flag or by creating a user-defined network and connecting containers to the network.</p><p>9. What is Docker Swarm?</p><p>Docker Swarm is a native clustering and orchestration solution provided by Docker. It allows you to create and manage a cluster of Docker nodes to deploy and scale applications.</p><p>10. What is the difference between Docker Swarm and Kubernetes?</p><p>Docker Swarm is a simpler and less feature-rich orchestration tool compared to Kubernetes. It is suitable for small to medium-sized deployments, while Kubernetes is more scalable and suitable for complex, large-scale deployments.</p><p>11. How do you scale Docker containers?</p><p>You can scale Docker containers manually by running multiple instances of the same container or use orchestration tools like Docker Swarm or Kubernetes to automatically scale the containers based on predefined rules.</p><p>12. How does Docker ensure security?</p><p>Docker provides security through isolation by using kernel namespaces and control groups. It also supports various security features such as user namespaces, seccomp, and AppArmor profiles.</p><p>13. What is the difference between a Docker container and an image?</p><p>An image is a template used to create containers. Containers are running instances of images that have their own filesystem and can be started, stopped, and managed.</p><p>14. How can you share Docker images with others?</p><p>You can share Docker images with others by pushing them to a Docker registry, such as Docker Hub or a private registry. Others can then pull the image from the registry to use it.</p><p>15. How do you manage data persistence in Docker?</p><p>Data persistence in Docker can be achieved by using Docker volumes or mounting host directories into containers. Docker volumes provide a way to manage and share data between containers and also persist data even if the containers are removed.</p><p>16. What is the purpose of Dockerfile’s ENTRYPOINT and CMD instructions?</p><p>The ENTRYPOINT instruction specifies the command that will be executed when the container starts. The CMD instruction provides default arguments to the entry point command.</p><p>17. How can you access logs from a Docker container?</p><p>You can access logs from a Docker container using the docker logs command followed by the container ID or name.</p><p>18. How can you pass environment variables to a Docker container?</p><p>You can pass environment variables to a Docker container using the -e flag followed by the variable name and value when running the docker run command.</p><p>19. What is the difference between a Docker image and a Docker container?</p><p>A Docker image is a static, read-only file that contains the application and its dependencies, while a Docker container is a running instance of an image that has its own state and can be started, stopped, and managed.</p><p>20. How do you remove Docker images and containers?</p><p>You can remove Docker images using the docker rmi command followed by the image ID or name. Containers can be removed using the docker rm command followed by the container ID or name.</p><p>21. What is Docker Registry?</p><p>Docker Registry is a service that stores and distributes Docker images. Docker Hub is the default public Docker Registry, but you can also set up your own private registry.</p><p>22. How can you update a Docker image?</p><p>To update a Docker image, you need to rebuild it with the necessary changes and then push the updated image to the Docker registry. Existing containers can be stopped and recreated with the new image.</p><p>23. What are Docker volumes?</p><p>Docker volumes are a way to persist data generated by and used by Docker containers. They provide a mechanism for managing and sharing data between containers, as well as persisting data even if the containers are removed.</p><p>24. How can you list Docker containers?</p><p>You can list Docker containers using the docker ps command. The -a flag can be used to display all containers, including the ones that are not currently running.</p><p>25. What is the purpose of Docker networks?</p><p>Docker networks provide a way to enable communication between containers running on the same host or across different hosts. They allow containers to discover and connect to each other using container names.</p><p>26. How do you update Docker containers?</p><p>To update a Docker container, you need to stop the existing container, pull the updated image from the Docker registry, and then start a new container with the updated image.</p><p>27. What is the difference between COPY and ADD instructions in a Dockerfile?</p><p>The COPY instruction in a Dockerfile copies files and directories from the build context to the image. The ADD instruction can do the same but also supports additional features like extracting tar archives and downloading files from URLs.</p><p>28. What is the role of a Dockerfile’s EXPOSE instruction?</p><p>The EXPOSE instruction in a Dockerfile informs Docker that the container listens on the specified network ports at runtime. It does not actually publish the ports to the host, but it is useful for documentation purposes and when creating container links.</p><p>29. What is the difference between Docker and Kubernetes?</p><p>Docker is a containerization platform that allows you to create, package, and run applications in containers. Kubernetes, on the other hand, is a container orchestration platform that automates the deployment, scaling, and management of containerized applications.</p><p>30. How can you clean up unused Docker resources?</p><p>You can clean up unused Docker resources using the docker system prune command. This command removes unused images, containers, volumes, and networks, freeing up disk space. Use it with caution, as it permanently deletes resources.</p><p>Hope you found this helpful. Do connect/ follow for more such content.</p><p>~ Chetan Rakhra.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38c5eba8b99c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps StoryTelling — 4 (Terraform)]]></title>
            <link>https://medium.com/@chetxn/devops-storytelling-4-terraform-b0b70f920ad?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0b70f920ad</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[projects]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Tue, 13 Jun 2023 15:40:04 GMT</pubDate>
            <atom:updated>2023-06-13T15:40:04.103Z</atom:updated>
            <content:encoded><![CDATA[<h3>DevOps StoryTelling — 4 (Terraform)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/1*DbKcQi-2Thg9K385buu0LQ.png" /></figure><p>Once upon a time, there was a Terraform developer named Charlie. Charlie loved infrastructure as code so much that he decided to write a Terraform configuration that could deploy a time machine to the cloud.</p><p>He spent months tinkering with his Terraform code, adding all sorts of futuristic technologies to his time machine until he had a module that could transport him to any point in time.</p><p>Excited to see his creation come to life, Charlie hit the “apply” button and watched as Terraform began to deploy his time machine. He stepped inside and set the dials to take him back to the Wild West.</p><p>But as soon as he arrived, he realized that something was not quite right. Instead of landing in the Wild West, he found himself in the middle of a space battle between aliens and humans.</p><p>Confused and scared, Charlie quickly realized that he had made a mistake in his Terraform configuration. Instead of sending him back in time, it had sent him to a parallel universe.</p><p>He tried to get back to his own universe, but the time machine was malfunctioning. It kept sending him to different parallel universes, each one more bizarre than the last.</p><p>He found himself in a universe where humans had evolved into cats, and another where robots ruled the world. He even ended up in a universe where everyone spoke in emojis.</p><p>In the end, Charlie realized that sometimes, it’s best to stick to the present. He decided to use his Terraform skills to create more practical infrastructure, like deploying web servers and databases.</p><p>And from that day forward, whenever he needed a break from coding, he would sit back and watch episodes of Marvel Comics, content in the knowledge that he would never have to worry about accidentally transporting himself to another universe again.</p><p>Blog Link: <br>GitHub Link: <a href="https://github.com/chxtan">https://github.com/chxtan</a></p><p>🚀 Follow for more DevOps content, tips and tricks, and Hands-On Project Implementation.</p><p>👍 Hit like, if you found it helpful!<br>🔖 Save it for the future!<br>📤 Share it with your connections!<br>💭 Comment your thoughts!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0b70f920ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps Project — 10 (Step-by-step Implementation)]]></title>
            <link>https://medium.com/@chetxn/devops-project-10-step-by-step-implementation-df2858a62036?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/df2858a62036</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Sun, 04 Jun 2023 13:28:48 GMT</pubDate>
            <atom:updated>2023-06-24T08:41:04.322Z</atom:updated>
            <content:encoded><![CDATA[<h3>DevOps Project — 11 (Step-by-step Implementation)</h3><p>Project 11: Build a website using AWS CodeCommit and AWS CodeBuild.</p><p>Here is the Architecture:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I5jRR-1RDXuTxS90" /></figure><p>1. First of all, to start with AWS DevOps, we need to create a user by using the IAM service with some specific access.</p><p>2. Storage — In this storage part we will store our built code for that we will use Artifacts or S3 buckets.</p><p>3. CodeCommit — CodeCommit is just like GitHub inside AWS. We can perform push, pull, branching on the repositories, and many other operations.</p><p>4. CodeBuild — Now, the pushed code in CodeCommit, should be built and tested (Continuous Integration (CI)). This will happen inside CodeBuild. And the built code will be stored in Storage.</p><p>Step-By-Step Implementation:</p><p>1. Goto the AWS console and search for “CodeCommit” and click on “Create Repository.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*CdSBvKqfmdhimSpl" /></figure><p>2. Enter the Name and Description then click on Create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*qHv5itzNFIM7b4jX" /></figure><p>3. The Repository was created successfully. But it is giving an error as “You cannot configure SSH using root account”.</p><p>4. Now, search for IAM and create one user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*Qr8AnLxs4CWtdAKJ" /></figure><p>5. Now, open the created user and search for “HTTPS Git credentials for AWS CodeCommit” and click on “Generate Credentials”.</p><p>It will generate the Username and Password.</p><p>6. Now, we will clone the “demo-app” repository that we have created in CodeCommit.</p><p>7. Click on “Clone URL” then “Clone HTTPS” and it will provide you the URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*KujGwrhRV3cY8-BS" /></figure><p>8. Now, go to your local computer and create a folder named “AWS DevOps” And open the terminal inside.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*NvKFHkQVJU3EAI-f" /></figure><p>9. Run, “git clone <a href="https://git-codecommit.us-west-1.amazonaws.com/v1/repos/demo-app">https://git-codecommit.us-west-1.amazonaws.com/v1/repos/demo-app</a>”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*K2LxLKfTOxyeJnEj" /></figure><p>10. It will ask for Username and Password. Enter it in the prompt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/0*hXukv1V2R9HKAX--" /></figure><p>11. Now add one file named “index.html”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*E46Az7aM1Qr35PNu" /></figure><p>12. Push it into the repository. And boom! Code will be reflected to the repository.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*AV_Rb9Gbht996d0O" /></figure><p>CodeBuild:</p><p>13. Now, here comes the CodeBuild. On LHS, click on “Build” then “Build projects”.</p><p>14. Click on “Create build project”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*jRVW2LzNsrxqVxTB" /></figure><p>15. Enter the Name and Description of the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*0fevt4vX3I8msaqQ" /></figure><p>16. In Source section, Select</p><p>Source provider: AWS CodeCommit.</p><p>Repository: demo-app</p><p>Reference Type: Branch</p><p>Branch: Main</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*iZxEPyRqRdTgxRE7" /></figure><p>17. In the Environment section, Select</p><p>Environment Image: Managed Image</p><p>Operating System: Ubuntu</p><p>Runtime: Standard</p><p>Image: &lt;latest one&gt;</p><p>18. For this, a Service Role will be required and it will create automatically when we will select the “New Service Role”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*sVsBBYmAVWv41RlJ" /></figure><p>19. In the BuildSpec section, click on “Use a buildspec file”.</p><p>20. Add a file named “buildspec.yaml” in the “demo-app” repository.</p><p>(Build file is basically a specification file, that will give the instructions, while building).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*YMefQxuQNDu6wM0t" /></figure><p>21. Now, the rest of the things leave as it is, and click on “Create Build Project”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/0*SrLYSDc6kzo4hpST" /></figure><p>22. Now, click on “Start Build”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*dTN2PVVf5-5Pwvfg" /></figure><p>23. Here, you can see the “Phase Details”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*KbKqes1k_cYh38Mo" /></figure><p>24. The code has been built.</p><p>25. We can give “Artifacts upload location” if we want to build the code on some specific location.</p><p>26. Goto “Edit” button and click on “Artifacts”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*8p9ecnF1HqHCJ6uQ" /></figure><p>27. Here, select</p><p>Type: S3 Bucket. (Create a new s3 bucket if you haven’t created it)</p><p>Bucket Name: &lt;Your created bucket&gt;</p><p>Name: &lt;Your folder name in S3 bucket&gt; (Go and create one)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*KqyCT4748y3jWE4q" /></figure><p>And click on “Update Artifact”.</p><p>28. Next time, whenever you will start a build, your files will go there.</p><p>29. Let’s give it a try by building it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/0*8FkpJosyHC2kkAGV" /></figure><p>30. Here, you can see artifacts.zip uploaded to S3 bucket successfully.</p><p>We will deploy this code with the help of “CodeDeploy” and automate it with “CodePipeline” in the next project article.</p><p>Hope you found this helpful. Do connect/ follow for more such content.</p><p>~ Chetan Rakhra.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df2858a62036" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DevOps StoryTelling — 3 (Linux )]]></title>
            <link>https://medium.com/@chetxn/devops-storytelling-3-linux-604c1d8dd84f?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/604c1d8dd84f</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cicd]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Wed, 24 May 2023 15:04:22 GMT</pubDate>
            <atom:updated>2023-05-24T15:07:06.713Z</atom:updated>
            <content:encoded><![CDATA[<h3>DevOps StoryTelling — 3 (Linux 🐧)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Z6_bAkzkoT-L1nGbyEUdAQ.gif" /></figure><p>Linux 🐧</p><p>Once in a town filled with tech enthusiasts, there was a computer geek named Sam. Sam loved tinkering with computers and was a huge fan of Linux, the operating system known for its flexibility and open-source nature.</p><p>One day, while Sam was experimenting with a new Linux distribution, something unexpected happened. As he clicked the install button, a puff of smoke appeared, and a tiny penguin named Penny materialized in front of him.</p><p>Penny had a mischievous grin and a mischievous sparkle in her eyes. She introduced herself as the Linux Fairy and said, “Congratulations, Sam! You have summoned me, the magical Linux Fairy. I’m here to grant you three wishes related to Linux!”</p><p>Sam couldn’t believe his luck. He thought for a moment and said, “Linux Fairy, for my first wish, I want the power to troubleshoot any Linux problem effortlessly.”</p><p>Penny nodded and waved her tiny wand. Instantly, Sam felt a surge of knowledge coursing through his veins. From that moment on, he could solve any Linux issue with ease, impressing his friends with his troubleshooting skills.</p><p>Excitedly, Sam made his second wish, “Linux Fairy, I wish for a laptop that never runs out of battery while I’m working on Linux projects.”</p><p>Penny tapped the laptop with her wand, and it started glowing with a soft, pulsating light. Sam’s laptop now had infinite battery life, allowing him to code for hours without worrying about losing power.</p><p>For his final wish, Sam grinned mischievously and said, “Linux Fairy, my last wish is to bring a little fun into the lives of all Linux users.”</p><p>Penny laughed and twirled her wand in the air. Suddenly, across the town, computers running Linux came alive with amusing desktop wallpapers, dancing penguins, and silly error messages that made everyone chuckle.</p><p>From that day forward, Linux users in the town had a playful spring in their steps. The Linux Fairy’s touch had transformed the realm of technology into a joyful playground, with laughter echoing through the air.</p><p>As for Sam, he continued to explore the wonders of Linux, sharing his knowledge and bringing smiles to the faces of fellow Linux enthusiasts. And every now and then, he would catch a glimpse of a mischievous penguin, reminding him of the magical encounter that had made his Linux journey even more memorable.</p><p>And so, in the world of technology, Linux became not just a powerful operating system but also a source of laughter and delight, all thanks to the whimsical Linux Fairy and her enchanting powers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=604c1d8dd84f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Healthy CICD Pipeline.]]></title>
            <link>https://medium.com/@chetxn/healthy-cicd-pipeline-b985f56be18?source=rss-9609085c0266------2</link>
            <guid isPermaLink="false">https://medium.com/p/b985f56be18</guid>
            <category><![CDATA[cicd]]></category>
            <category><![CDATA[pipeline]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Chetan Rakhra]]></dc:creator>
            <pubDate>Sat, 20 May 2023 15:08:46 GMT</pubDate>
            <atom:updated>2023-05-20T15:14:16.640Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*moGvfe-CSq1cAazqcH4STQ.gif" /></figure><p>Building a healthy CI/CD pipeline involves following best practices and implementing certain key elements. Here are some points to consider for a healthy CI/CD pipeline:</p><p>1. Automated Testing: Implement a comprehensive suite of automated tests, including unit tests, integration tests, and end-to-end tests, to ensure the quality and stability of your codebase.</p><p>2. Version Control: Use a robust version control system like Git to manage your source code, configurations, and scripts. Maintain a clear and organized repository structure.</p><p>3. Continuous Integration: Set up a CI server to automatically build and test your code whenever changes are committed to the repository. This ensures that new code is integrated smoothly and prevents integration issues.</p><p>4. Deployment Automation: Automate the deployment process to eliminate manual errors and reduce deployment time. Use tools like Ansible, Kubernetes, or Docker to streamline and standardize deployments.</p><p>5. Infrastructure as Code: Adopt Infrastructure as Code (IaC) principles to manage your infrastructure and configuration. Tools like Terraform or CloudFormation can help automate the provisioning and management of your infrastructure.</p><p>6. Configuration Management: Utilize configuration management tools such as Puppet, Chef, or Ansible to manage and enforce consistent configurations across your environments.</p><p>7. Continuous Delivery: Aim to achieve continuous delivery, where you can release software changes to production at any time with confidence. Automate the deployment process and focus on maintaining a stable and reliable pipeline.</p><p>8. Monitoring and Alerting: Implement monitoring and alerting systems to proactively identify and respond to issues in your pipeline. Monitor key metrics, logs, and performance indicators to ensure optimal pipeline health.</p><p>9. Security and Compliance: Integrate security checks and compliance measures into your pipeline. Conduct regular security assessments, and vulnerability scans, and ensure adherence to regulatory requirements.</p><p>10. Feedback Loop: Foster a culture of feedback and continuous improvement. Encourage collaboration among development, testing, and operations teams to identify bottlenecks, address pain points, and optimize the pipeline.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b985f56be18" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>