<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Chethan</title>
    <description>The latest articles on DEV Community by Chethan (@chethanblgs99).</description>
    <link>https://dev.to/chethanblgs99</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3452602%2Fa50749b2-82c1-43e1-826a-dbb3bb5f7ca8.png</url>
      <title>DEV Community: Chethan</title>
      <link>https://dev.to/chethanblgs99</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chethanblgs99"/>
    <language>en</language>
    <item>
      <title>Understanding Kubernetes Architecture: A Simple Breakdown</title>
      <dc:creator>Chethan</dc:creator>
      <pubDate>Wed, 03 Dec 2025 16:00:01 +0000</pubDate>
      <link>https://dev.to/chethanblgs99/understanding-kubernetes-architecture-a-simple-breakdown-5aph</link>
      <guid>https://dev.to/chethanblgs99/understanding-kubernetes-architecture-a-simple-breakdown-5aph</guid>
      <description>&lt;p&gt;Understanding the Kubernetes architecture has given me a solid foundation for diving deep into the world of container orchestration🐋. I've synthesized the core components into an easy-to-follow guide. This is the complete breakdown of the Kubernetes architecture☸️👇:&lt;/p&gt;

&lt;p&gt;Kubernetes follows a client-server architecture🛜. It mainly has two components:&lt;/p&gt;

&lt;p&gt;📌Control plane: It is the master node responsible for maintaining the state of the cluster.&lt;br&gt;
📌Data plane: It is a collection of worker nodes that are responsible for running your applications.&lt;/p&gt;

&lt;p&gt;The control plane has the following components:&lt;/p&gt;

&lt;p&gt;📌Kube-apiserver: Exposes the Kubernetes API, serving as the front-end for the Control Plane.&lt;br&gt;
📌Kube-scheduler: Watches for newly created Pods and assigns them to suitable Worker Nodes based on requirements, constraints, etc.&lt;br&gt;
📌 Kube-controller-manager: It is responsible for running various controller processes, such as Replication controllers, Node controllers, etc.&lt;br&gt;
📌Cloud-controller-manager: It integrates Kubernetes with cloud provider APIs to manage cloud resources like persistent volumes.&lt;/p&gt;

&lt;p&gt;The data plane has the following components:&lt;/p&gt;

&lt;p&gt;📌Container runtime: Software responsible for running containers, such as Docker or CRI-O. &lt;br&gt;
📌Kubelet: An agent that runs on each node and communicates with the Control Plane. It ensures that containers are running in Pods.&lt;br&gt;
📌Kube-proxy: It maintains network rules on the nodes, enabling network communication to and from Pods, and facilitating Service discovery.&lt;/p&gt;

</description>
      <category>devops</category>
      <category>kubernetes</category>
      <category>containers</category>
      <category>cloudnative</category>
    </item>
    <item>
      <title>Understanding Linux Permissions: A Beginner-Friendly Guide for DevOps 🚀</title>
      <dc:creator>Chethan</dc:creator>
      <pubDate>Thu, 04 Sep 2025 13:10:08 +0000</pubDate>
      <link>https://dev.to/chethanblgs99/understanding-linux-permissions-a-beginner-friendly-guide-for-devops-3mbj</link>
      <guid>https://dev.to/chethanblgs99/understanding-linux-permissions-a-beginner-friendly-guide-for-devops-3mbj</guid>
      <description>&lt;p&gt;One of the most important concepts that I and many beginners encountered was File Permissions. These topics are super important if you want to become handy with handling Linux files. In this blog, I will deep dive and provide a brief overview of Linux File permissions and help others learn it fast.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F64vr42gxt2ljehb5ej1i.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F64vr42gxt2ljehb5ej1i.png" alt=" " width="800" height="984"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📌&lt;strong&gt;Listing File Permissions:&lt;/strong&gt;&lt;br&gt;
To check permissions of a file use: ls -l&lt;br&gt;
Files in Linux have different types:&lt;/p&gt;

&lt;p&gt;1) - → regular file&lt;br&gt;
2) d → directory&lt;br&gt;
3) l → symbolic link (e.g., lrwxrwxrwx 1 root root 7 Aug 26 10:00 lib -&amp;gt; usr/lib)&lt;/p&gt;

&lt;p&gt;In the permissions string (rwxr-xr-x):&lt;br&gt;
1) r → read&lt;br&gt;
2) w → write&lt;br&gt;
3) x → execute&lt;/p&gt;

&lt;p&gt;The string is divided into 3 sets:&lt;br&gt;
1) User (owner)&lt;br&gt;
2) Group&lt;br&gt;
3) Others&lt;/p&gt;

&lt;p&gt;So rwxr-xr-x means: owner can read, write, execute; group can read &amp;amp; execute; others can read &amp;amp; execute.&lt;/p&gt;

&lt;p&gt;🔑&lt;strong&gt;Changing Permissions with chmod:&lt;/strong&gt;&lt;br&gt;
Permissions can be set numerically or symbolically:&lt;/p&gt;

&lt;p&gt;1) Numeric (octal method)&lt;br&gt;
r = 4, w = 2, x = 1&lt;br&gt;
&lt;strong&gt;Eg&lt;/strong&gt;:  To give all permissions to all sets of users: chmod 777 file.txt&lt;/p&gt;

&lt;p&gt;2) Symbolic (using letters) &lt;br&gt;
&lt;strong&gt;Eg&lt;/strong&gt;:&lt;br&gt;
 1) To give read permission to the user: chmod u+r file.txt &lt;br&gt;
2) To give read permissions to both the group and others: chmod go+r file.txt&lt;/p&gt;

&lt;p&gt;To remove permission use '-' : chmod g-r file.txt&lt;/p&gt;

&lt;p&gt;⚙️&lt;strong&gt;Default Permissions with unmask:&lt;/strong&gt;&lt;br&gt;
When a new file is created, its default permissions depend on the umask value.&lt;/p&gt;

&lt;p&gt;Default mask : 022&lt;br&gt;
To change it : umask 021 (This removes read permission from group and execute permission from others)&lt;/p&gt;

&lt;p&gt;🔒&lt;strong&gt;Special Permission Bits:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Linux also supports advanced permission bits:&lt;br&gt;
1) SUID (Set User ID) – executable runs with file owner’s privileges : &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Eg&lt;/strong&gt;: chmod u+s file.txt , chmod 4555 file.txt&lt;/p&gt;

&lt;p&gt;2) SGID (Set Group ID) - Here there are two cases:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;On files → runs with file group privileges&lt;/li&gt;
&lt;li&gt;On directories → new files inherit directory’s group&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Eg&lt;/strong&gt;: chmod g+s file.txt , chmod 2777 file.txt&lt;/p&gt;

&lt;p&gt;3) Sticky Bit – on directories, prevents deletion of files by anyone except the owner&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Eg&lt;/strong&gt; : chmod +t dir , chmod 1755 file.txt&lt;/p&gt;

&lt;p&gt;👥&lt;strong&gt;Change Ownership:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;1) Change file owner. &lt;strong&gt;Eg&lt;/strong&gt;: chown newuser filename&lt;br&gt;
2) Change group ownership. &lt;strong&gt;Eg&lt;/strong&gt;:chown :newgroup filename&lt;br&gt;
3) Change both. &lt;strong&gt;Eg&lt;/strong&gt;:chown -R newuser:newgroup director&lt;/p&gt;

&lt;p&gt;To change group: &lt;/p&gt;

&lt;p&gt;1) For a single file. &lt;strong&gt;Eg&lt;/strong&gt;: chgrp newgroup filename&lt;br&gt;
2) For all files in directory. &lt;strong&gt;Eg&lt;/strong&gt;: chgrp -R newgroup directory/&lt;/p&gt;

&lt;p&gt;This was my learning summary on Linux permissions. If you’re also exploring DevOps/Linux, practicing these commands hands-on will help things click much faster. Do share it with your newtork and share your thoughts on this 🙌&lt;/p&gt;

&lt;p&gt;👉 Which of these file permissions do you use the most ?&lt;/p&gt;

</description>
      <category>devops</category>
      <category>linux</category>
      <category>learning</category>
      <category>opensource</category>
    </item>
    <item>
      <title>A Beginner’s Guide to the Linux File System Hierarchy 🚀</title>
      <dc:creator>Chethan</dc:creator>
      <pubDate>Mon, 01 Sep 2025 13:09:51 +0000</pubDate>
      <link>https://dev.to/chethanblgs99/a-beginners-guide-to-the-linux-file-system-hierarchy-7oo</link>
      <guid>https://dev.to/chethanblgs99/a-beginners-guide-to-the-linux-file-system-hierarchy-7oo</guid>
      <description>&lt;p&gt;When I first started exploring Linux, one of the things that confused me most was the file system layout. Unlike Windows, where everything is neatly tucked under C:\, Linux starts with a single root directory /, and from there, everything branches out into different subfolders with very specific purposes.&lt;/p&gt;

&lt;p&gt;At first glance, it can feel overwhelming — why are there so many folders, and what do they all mean? But once you understand the logic behind the structure, navigating Linux becomes a lot more intuitive.&lt;/p&gt;

&lt;p&gt;Let’s take a quick tour of the key directories in the Linux file system 👇&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo0uy8mc360p6xfcmwkno.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fo0uy8mc360p6xfcmwkno.png" alt=" " width="800" height="963"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/bin&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Essential binaries needed to boot and run basic commands.&lt;br&gt;
Eg: ls, cp, cat&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/sbin&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;System binaries and admin tools, mainly for the root user.&lt;br&gt;
Eg: ip, mount, fdisk&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/lib&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Shared libraries and kernel modules required by /bin and /sbin.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/etc&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Configuration files for the system and applications.&lt;br&gt;
Eg: passwd, hosts&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/home&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Personal workspace for each user — your familiar "home directory."&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/dev&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Device files that act as an interface to hardware.&lt;br&gt;
Eg: sda, sdb&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/root&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Home directory for the root (superuser).&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/var&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Variable files like logs, caches, and backups.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/usr&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;User-installed applications, binaries, and source code.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/tmp&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Temporary files (wiped after reboot, with sticky bit).&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/boot&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Bootloader files required to start the operating system.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/proc&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Virtual file system exposing kernel and process info.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/sys&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Virtual file system for interacting with devices and drivers.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/run&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Runtime process data since the last reboot.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/mnt&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Temporary mount point for sysadmins.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;/media&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Mount point for removable devices like USBs, DVDs, CDs.&lt;/p&gt;

&lt;p&gt;As I’m learning Linux, I’m curious:&lt;br&gt;
👉 Which of these directories do you use or explore the most, and why?&lt;/p&gt;

&lt;p&gt;I’d love to hear your experiences and tips — feel free to share them in the comments! 🙌&lt;/p&gt;

</description>
      <category>devops</category>
      <category>linux</category>
      <category>learning</category>
    </item>
    <item>
      <title>Starting my Tech Journey 💪</title>
      <dc:creator>Chethan</dc:creator>
      <pubDate>Fri, 22 Aug 2025 12:16:45 +0000</pubDate>
      <link>https://dev.to/chethanblgs99/starting-my-tech-journey-4eog</link>
      <guid>https://dev.to/chethanblgs99/starting-my-tech-journey-4eog</guid>
      <description>&lt;p&gt;Hi Folks,&lt;br&gt;
My name is Chethan, a second-year undergrad passionate to learn about &lt;strong&gt;DevOps&lt;/strong&gt; and &lt;strong&gt;Cloud-Native&lt;/strong&gt; tools. Today, I am happy to share that I will be starting my journey where I will be sharing my learnings with you and learn from others as well, and growing as an Engineer. &lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

</description>
      <category>devops</category>
      <category>devsecops</category>
      <category>softwaredevelopment</category>
      <category>learninpublic</category>
    </item>
  </channel>
</rss>
