<?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 Subathra  on Medium]]></title>
        <description><![CDATA[Stories by Subathra  on Medium]]></description>
        <link>https://medium.com/@subathra.t2021csbs?source=rss-19df0fb0d778------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Su9DfGnln8OQiWUbpMDOtA.jpeg</url>
            <title>Stories by Subathra  on Medium</title>
            <link>https://medium.com/@subathra.t2021csbs?source=rss-19df0fb0d778------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:33:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@subathra.t2021csbs/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[Docker to Kubernetes: Understanding the Evolution and Key Features]]></title>
            <link>https://medium.com/@subathra.t2021csbs/docker-to-kubernetes-understanding-the-evolution-and-key-features-f87e08093895?source=rss-19df0fb0d778------2</link>
            <guid isPermaLink="false">https://medium.com/p/f87e08093895</guid>
            <dc:creator><![CDATA[Subathra ]]></dc:creator>
            <pubDate>Sun, 21 Jul 2024 17:27:28 GMT</pubDate>
            <atom:updated>2024-07-21T17:27:28.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*lfGsa00ejw3-1XpLTVKPrg.png" /></figure><h3>Hey Everyone! 👋</h3><p>In today’s blog, we will dive into the concept of <strong>Kubernetes</strong>, exploring its <strong>history</strong> and the reasons behind its introduction. We’ll also discuss some of its key features, including its <strong>single-host nature</strong>, <strong>auto-healing capabilities</strong>, <strong>auto-scaling nature</strong>, and <strong>enterprise-level support</strong>. Additionally, we’ll examine why the industry has been transitioning from <strong>Docker</strong> to <strong>Kubernetes</strong> for container orchestration.</p><h3>🌟 The History of Kubernetes</h3><p>Kubernetes, often referred to as <strong>K8s</strong>, was originally developed by <strong>Google</strong> and later donated to the <strong>Cloud Native Computing Foundation (CNCF)</strong> in 2014. The project started as an internal solution at Google, known as <strong>Borg</strong>, which managed containerized applications across a vast number of servers. The need for a robust system to orchestrate and manage these containers led to the creation of Kubernetes. Since then, it has become the <strong>de facto standard</strong> for container orchestration.</p><h3>🤔 Why Was Kubernetes Introduced?</h3><p>Kubernetes was introduced to address several challenges associated with deploying, managing, and scaling containerized applications:</p><ol><li><strong>Scalability</strong>: As applications grow, managing them manually becomes cumbersome. Kubernetes automates the scaling process, ensuring applications can handle increased traffic without manual intervention.</li><li><strong>Resilience</strong>: Containers can fail, and when they do, it’s crucial to have a system that can automatically detect and recover from these failures. Kubernetes provides <strong>auto-healing capabilities</strong> to ensure applications remain available and performant.</li><li><strong>Portability</strong>: Applications need to run consistently across different environments, whether on-premises or in the cloud. Kubernetes abstracts the underlying infrastructure, providing a <strong>consistent environment</strong> for applications.</li></ol><h3>🐳 From Docker to Kubernetes: Why the Transition?</h3><p><strong>Docker</strong> revolutionized the way we build, ship, and run applications by introducing containers. However, as applications grew in complexity, managing containers across multiple environments became challenging. This is where <strong>Kubernetes</strong> comes in:</p><ol><li><strong>Orchestration</strong>: While Docker is excellent for building and running containers, it doesn’t provide built-in orchestration capabilities. Kubernetes, on the other hand, excels at <strong>orchestrating containers</strong> across multiple hosts, managing their lifecycle, and ensuring they are running as expected.</li><li><strong>Scaling</strong>: Docker Swarm, Docker’s native clustering and scheduling tool, is often compared to Kubernetes. However, Kubernetes offers more robust and granular control over <strong>scaling applications</strong>. It can automatically scale applications based on resource usage, making it more suitable for large-scale deployments.</li><li><strong>Flexibility</strong>: Kubernetes provides a higher level of abstraction for managing containerized applications. It supports a wide range of container runtimes and integrates seamlessly with various infrastructure providers, giving it an edge over Docker’s more limited ecosystem.</li><li><strong>Community and Ecosystem</strong>: Kubernetes has a vibrant and growing community, with extensive support from major cloud providers like AWS, Google Cloud, and Azure. This extensive ecosystem ensures continuous development, frequent updates, and a wealth of resources for developers and operators.</li></ol><h3>🔑 Key Features of Kubernetes</h3><ol><li><strong>Single-Host Nature</strong> 🖥️</li></ol><p>Kubernetes allows you to manage applications across a single host or multiple hosts. This flexibility is vital for development and testing environments where running on a single host is sufficient. For production environments, Kubernetes seamlessly scales across multiple hosts, ensuring <strong>high availability</strong> and <strong>fault tolerance</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1AL3EB7FailOUMLK2yzbrQ.png" /></figure><p><strong>2. Auto-Healing Capabilities</strong> 🔄</p><p>One of the standout features of Kubernetes is its <strong>auto-healing capabilities</strong>. When a container fails, Kubernetes automatically restarts it. If a node fails, it redistributes the containers to healthy nodes. This ensures that your application remains up and running without manual intervention, enhancing reliability and reducing downtime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*dV7mxtTy7G4UAkAWuNNHkQ.png" /></figure><p><strong>3. Auto-Scaling Nature</strong> 📈</p><p>Kubernetes can automatically <strong>scale your applications</strong> based on the current load. Using the <strong>Horizontal Pod Autoscaler</strong>, Kubernetes adjusts the number of running pods in response to CPU utilization or other select metrics. This ensures that your application can handle varying levels of traffic efficiently, providing resources when needed and scaling down to save costs during low traffic periods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9TiXQkdqQPNqTvE5-eiGag.png" /></figure><p><strong>4. Enterprise-Level Support</strong> 🏢</p><p>Kubernetes has robust <strong>enterprise-level support</strong> from major cloud providers and software vendors. It integrates seamlessly with various tools and platforms, making it easier for enterprises to adopt and integrate Kubernetes into their existing workflows. Additionally, the extensive community support and continuous development ensure that Kubernetes remains up-to-date with the latest features and security enhancements.</p><h3>📚 Conclusion</h3><p>Kubernetes has revolutionized the way we deploy, manage, and scale containerized applications. Its origins at Google and subsequent development by the open-source community have made it a powerful and reliable tool for both small and large-scale deployments. By understanding its history and key features, you can better appreciate why Kubernetes is such a vital component in modern cloud-native applications.</p><p>Stay tuned for more insights and deep dives into the world of Kubernetes in our upcoming blogs. Happy learning! 🎉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f87e08093895" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Git for DevOps]]></title>
            <link>https://medium.com/@subathra.t2021csbs/mastering-git-for-devops-3d981c52c5e3?source=rss-19df0fb0d778------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d981c52c5e3</guid>
            <dc:creator><![CDATA[Subathra ]]></dc:creator>
            <pubDate>Sat, 13 Jul 2024 10:21:43 GMT</pubDate>
            <atom:updated>2024-07-13T10:21:43.944Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*WXYphNF6QoxWXeJma0ugnA.png" /></figure><h3>Version Control Systems: Then and Now</h3><p>In the past, we used tools like <strong>SubVersion</strong> and <strong>Concurrent Versions System (CVS)</strong> for version control. These older systems had limited features and didn’t offer much support for code collaboration and duplication.</p><p>To address these limitations, modern version control systems such as <strong>Git</strong>, <strong>GitHub</strong>, <strong>BitBucket</strong>, and <strong>GitLab</strong> were developed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*25106YEZ1QXSOVLm8L6U9g.png" /></figure><h3>The Major Difference Between Git and GitHub</h3><p>The major difference between <strong>Git</strong> and <strong>GitHub</strong> is:</p><ul><li><strong>Git</strong> is a version control system that tracks changes in your code.</li><li><strong>GitHub</strong> is a platform built on top of Git, offering additional features that make it easier for multiple developers to collaborate, share ideas, and contribute to projects. It also allows public visibility of your projects and profiles, making it easy for others to see and contribute to your work if you choose to make them public.</li></ul><h3>Git for DevOps</h3><p>As today’s blog focuses on <strong>Git for DevOps</strong>, let’s dive into that.</p><p><strong>GitHub</strong> is essential for every DevOps engineer. It’s used daily for various tasks like automation, testing, and more. Here are some important <strong>Git commands</strong> to know:</p><p>To authenticate with your CLI to GitHub there are 3 optionas available.</p><ul><li>SSH 🔑</li><li>HTTPS 🌐</li><li>GitHub CLI 🛠️</li></ul><h3>Using SSH 🔐</h3><p>You can go to the GitHub UI</p><p>1.There is a profile icon located in the right-most top corner,click on that</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oOVncvb1la3MoC1oyn4bdQ.png" /></figure><p>2. It will give a below pop-up options,click on Settings option</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/298/1*3IFqyFs2Jpjo12DZuEAL-A.png" /></figure><p>3. Then click on SSH-GPG keys</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/1*6h4sY-1zkilAaVSJoqOtXg.png" /></figure><p>If you have your already secret keys , you can use that else use the below command to generate the secret keys in the CLI</p><pre>ssh-keygen -t rsa<br>#-t flag denotes of type rsa</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*hLbZ9HLw69s5es515-cmDw.png" /><figcaption>While doing this mention the path where you need to store your key file.In my case,its the default file path.</figcaption></figure><p>4.Navigate to the <strong><em>.ssh</em></strong> folder and copy the contents of <strong><em>id_rsa.pub</em></strong> file</p><pre>cat  /id_rsa.pub/path</pre><p>5. Paste the copied contents in the Key field,and add Title to your file</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HPoAgJ7NKSuUEHec4_gMMQ.png" /></figure><h3>By using HTTPS method 🌍</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/467/1*cWrqxEjXvzDTC1F0r1kGpA.png" /></figure><p>You can copy the https link for your gitHub repo and go to the CLI and</p><pre>git clone repo_link</pre><p>The above command will download the gitHub repo link into your local.</p><pre>git fork repo_link</pre><p>The above command will create a copy of your gitHub repo</p><h3>Using GitHub CLI</h3><p>To authenticate using the GitHub CLI:</p><ol><li>Install GitHub CLI (gh)</li><li>Authenticate with:</li></ol><pre>gh auth login</pre><p>3. Clone your repository using:</p><pre>gh repo clone username/repo</pre><h3><strong>BRANCHING STRATEGIES </strong>🌿</h3><p>Navigate to the folder where you want to locate you git files ,its done by using cd command.</p><pre>cd /path/</pre><pre>git init</pre><p>The above command will initialize an empty git repository .</p><p>Once above step is executed we can find a .git folder created ,its viewed by</p><pre>ls -a</pre><p>The above command will list all the hidden folders as well.You can find .git folder.</p><p>In the <strong><em>.git folder</em></strong>, you can able to see there are 5 different files.You can view that by using ,</p><pre>ls /path/.git/</pre><p>The files are</p><p>👉 head 📌</p><p>Points to the current branch.</p><p>👉 hooks 🪝</p><p>Used to prevent storing of secret files by using pre-commits.</p><p>👉 configs ⚙️</p><p>Used to store some kind of secrets,passwords,credentials.</p><p>👉 objects 📦</p><p>Everything in Git is viewed as objects (the files,folders)</p><p>👉 refs 🔗</p><p>References to branches and tags.</p><h3>Creating and Managing Branches 🌱</h3><pre>git branch branch_name<br>git checkout -b branch_name</pre><p>Once branch is created ,you can switch into the branch</p><pre>git switch branch_name</pre><p>To commit the changes 📝</p><pre>git commit -m &quot;commit message&quot;</pre><h3>TRACKING FILES 📂</h3><p>Tracking files helps us to know the added changes.</p><p>To do this:</p><pre>git add tracking_file_name</pre><h3>Logging 📜</h3><p>To get log details of the files, which give us commit messages and commit IDs:</p><pre>git log file_name</pre><p>The above command will tell you,</p><ul><li>How many files are there?</li><li>Which files are tracked and those files which files are not tracked..</li></ul><h3>Checking Status 🔍</h3><p>To check the status of the files:</p><pre>git status</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/608/1*HmE2L-1jD7TjYra_JzcoNg.png" /></figure><h3>Stashing 📦</h3><p>Sometimes, you might need to switch branches, but you have uncommitted changes that you want to save for later. This is where stashing comes in…</p><p>To stash your changes:</p><pre>git stash</pre><p>This command will save your changes and clean your working directory. You can apply the stashed changes later by using:</p><pre>git stash apply</pre><p>To view the list of stashes:</p><pre>git stash list</pre><p>To apply a specific stash from the list:</p><pre>git stash apply stash@{index}</pre><h3>Branching Strategies 🌳</h3><p>The three common branching strategies are</p><ul><li><strong><em>Merging</em></strong></li><li><strong><em>Rebase</em></strong></li><li><strong><em>Cherry-Pick</em></strong></li></ul><h3>Merging ➕</h3><p>In merging, there is no specific order of commits. It simply combines changes from different branches.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*6ta1duXBNtJ5ntgy-eiaZA.png" /></figure><h3>Rebase 🔄</h3><p>In rebase, commits are maintained in a sequential order, providing a clean and linear history.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*jBXcz_ao2cF8YDxQPDFACw.png" /></figure><h3>Cherry-pick 🍒</h3><p>Cherry-picking is used to apply specific commits from one branch to another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*A5F0-cZ0cEyeIVQXeZs1HA.png" /><figcaption><strong>BEFORE CHERRY-PICK</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*mCH6EP_UJbxiPuEOt0vhcA.png" /><figcaption><strong>AFTER CHERRY-PICK</strong></figcaption></figure><p>— — — — — — — — —Thank you for reading! 😊 — — — — — — — — — — — — — — —</p><p>— — — — — — — — — — Have a great day ahead! 🌟 — — — — — — — — — — — — —</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d981c52c5e3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple Route53 :)]]></title>
            <link>https://medium.com/@subathra.t2021csbs/simple-route53-7c6ef085759f?source=rss-19df0fb0d778------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c6ef085759f</guid>
            <dc:creator><![CDATA[Subathra ]]></dc:creator>
            <pubDate>Wed, 01 May 2024 14:29:15 GMT</pubDate>
            <atom:updated>2024-05-01T14:29:15.179Z</atom:updated>
            <content:encoded><![CDATA[<h3>Simple Route53 :)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/278/1*YVrr9iYrumu-KyxiuDqBLQ.jpeg" /></figure><p>Hey guys!!<br>I would like to explain the concept of Route53 in simple….Let us walk together through my blog..</p><p>Firstly Route53 in aws denotes the DNS as a Service.Here’s how..<br>When the user sends any request to the application the flow is as follows<br>Internet Gateway -&gt; Route53 -&gt; In the Public Subnets we have NAT and Load Balancers -&gt; Private subnets<br>From the flow Route53’s work is like when an user for an instance tries to access the flipkart.com , amazon.com so on ,it has to convert the domain name i.e like flipkart.com into an ip address of a load balancer.Its because its hectic for the users to remember all the ip address instead of accessing them like a piece of cake by the domain names.So the users always tries to access only through the Domain names.Thus the Route53 takes care of this translation into a load balacers’s ip address.</p><p>How to register our domain names in AWS Route53?<br>1.If you already have a domain name purchased form GoDaddy or some other else ,aws can integrate it ,or if you are going to purchase a new domain<br>2.This step is mandatory i.e Hosting Zones in which the aws can have the DNS records that maps the domain name into an ip address</p><p>— — — — — — — — -Its how the Route53 functions — — — — — — — — — — <br>Also it performs Health Checks by sending request like 2mins once or 5mins once to web server to check the condition of the web servers,if it is good ,it will forward the traffic,and if we have more instances ,it will balance the traffic..</p><p>Thank you for your valuable time here .But its a simple concept of Route53 ,there is also a vast complexity too…Happy reading!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c6ef085759f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>