<?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 Abdulmcybersec on Medium]]></title>
        <description><![CDATA[Stories by Abdulmcybersec on Medium]]></description>
        <link>https://medium.com/@abdulmcybersec?source=rss-1310e4098eb8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Abdulmcybersec on Medium</title>
            <link>https://medium.com/@abdulmcybersec?source=rss-1310e4098eb8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:17:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abdulmcybersec/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[From Kubernetes Beginner to Security Professional: A Practical KCSA-Focused Guide]]></title>
            <link>https://medium.com/@abdulmcybersec/from-kubernetes-beginner-to-security-professional-a-practical-kcsa-focused-guide-934adfee594f?source=rss-1310e4098eb8------2</link>
            <guid isPermaLink="false">https://medium.com/p/934adfee594f</guid>
            <dc:creator><![CDATA[Abdulmcybersec]]></dc:creator>
            <pubDate>Thu, 23 Jul 2026 11:42:11 GMT</pubDate>
            <atom:updated>2026-07-23T11:42:11.625Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 1: Why Kubernetes Exists: From Virtual Machines to Containers</h3><p>A container includes:</p><ul><li>Application code</li><li>Libraries</li><li>Dependencies</li><li>Configuration</li></ul><p>Everything needed to run the application.</p><p>A simple comparison:</p><p>A virtual machine is like owning a complete house.</p><p>A container is like having your own apartment inside a building.</p><p>You have isolation, but you share some infrastructure.</p><p>Example:</p><ul><li>Physical Server</li><li>Operating System</li><li>Container Runtime</li></ul><p>— — — — — — — — —</p><p>Container 1<br>Application A</p><p>Container 2<br>Application B</p><p>Container 3<br>Application C</p><p>— — — — — — — — — -</p><p>Containers are:</p><ul><li>Faster to start</li><li>Smaller</li><li>Easier to move</li><li>More efficient</li></ul><h4>Docker Made Containers Popular</h4><p>Docker simplified the process of building and running containers.</p><p>Developers create an image that contains the application.</p><p>Example: Application Image + Runtime + Libraries + Application Code</p><p>The image is a blueprint.</p><p>The running version is called a container.</p><p>One image can create many containers.</p><p>Image:</p><p>|<br> | — — — Container 1<br> |<br> | — — — Container 2<br> |<br> | — — — Container 3</p><p>The New Problem: Too Many Containers</p><p>Containers solved application packaging, but companies quickly faced another challenge.</p><p>Imagine running:</p><p>Frontend: 100 containers</p><p>Backend: 200 containers</p><p>Payment Service: 50 containers</p><p>Database: 20 containers</p><p>Now you have hundreds of containers.</p><p>Questions appear:</p><ul><li>What happens if a container crashes?</li><li>Which server should run it?</li><li>How do we update applications safely?</li><li>How do we handle more traffic?</li><li>How do we secure everything?</li></ul><p>Managing this manually does not scale.</p><h4>Here Enters Kubernetes</h4><p>Kubernetes is a container orchestration platform.</p><p>Its job is to manage containers automatically.</p><p>You tell Kubernetes what you want:</p><p>Example: I need 5 copies of my website.</p><p>Kubernetes makes sure five copies are running.</p><p>If one fails:</p><p>Container crashed</p><p>↓</p><p>Kubernetes detects it</p><p>↓</p><p>Creates a replacement</p><p>If traffic increases:</p><p>More users</p><p>↓</p><p>Create more containers</p><p>↓</p><p>Handle more traffic</p><p>Kubernetes continuously compares:</p><p><strong>What you want</strong></p><p>with</p><p><strong>What is running</strong></p><p>and fixes differences automatically.</p><h4>Simple Real-World Example</h4><p>Imagine an online shopping application.</p><p>It has:</p><ul><li>Frontend</li><li>Backend API</li><li>Database</li><li>Payment Service</li></ul><p>Without Kubernetes:</p><ul><li>Engineers manually manage servers</li><li>Failures require manual recovery</li><li>Scaling takes time</li></ul><p>With Kubernetes:</p><p>You define:</p><ul><li>Frontend: 5 containers</li><li>Backend: 5 containers</li><li>Payment Service: 3 containers</li></ul><p>Kubernetes maintains this state.</p><p>If a server fails, Kubernetes moves workloads.</p><p>If demand increases, Kubernetes scales applications.</p><p>Why Kubernetes Security Matters</p><p>Kubernetes makes applications easier to manage, but it also creates new security responsibilities.</p><p>A Kubernetes security professional must protect:</p><p>Container Images</p><p>A vulnerable image can introduce security problems.</p><p>Example:</p><p>Old software package</p><p>↓</p><p>Known vulnerability</p><p>↓</p><p>Attacker exploits application</p><p>Access Control</p><p>Not everyone should have administrator access.</p><p>Kubernetes uses:</p><ul><li>Authentication</li><li>Authorization</li><li>RBAC</li></ul><p>to control who can do what.</p><p>Secrets</p><p>Applications need sensitive information:</p><ul><li>Database passwords</li><li>API keys</li><li>Certificates</li></ul><p>These must be protected properly.</p><p>Network Communication</p><p>A compromised application should not automatically access everything.</p><p>Network controls limit communication between workloads.</p><p>Runtime Security</p><p>Security does not end after deployment.</p><p>You must monitor:</p><ul><li>Suspicious behavior</li><li>Unauthorized processes</li><li>Unexpected network activity</li><li>The Kubernetes Security Mindset</li></ul><p>A Kubernetes security engineer always asks:</p><p><strong>Who can access the cluster?</strong></p><p><strong>What permissions do they have?</strong></p><p><strong>Are containers running safely?</strong></p><p><strong>Are images trusted?</strong></p><p><strong>Are secrets protected?</strong></p><p><strong>Can we detect and respond to attacks?</strong></p><p>Final Thoughts</p><p>The journey to Kubernetes started because organizations needed a better way to run applications.</p><p>The evolution was:</p><p>Physical Servers</p><p>↓</p><p>Virtual Machines</p><p>↓</p><p>Containers</p><p>↓</p><p>Kubernetes</p><p>Containers solved application packaging.</p><p>Kubernetes solved container management.</p><p>Kubernetes security ensures those applications remain protected.</p><p>In the next part, we will explore Kubernetes architecture and understand how every component works together:</p><ul><li>Control Plane</li><li>Worker Nodes</li><li>API Server</li><li>Scheduler</li><li>Controller Manager</li><li>etcd</li><li>kubelet</li><li>kube-proxy</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=934adfee594f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>