<?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 Fabio Ronca on Medium]]></title>
        <description><![CDATA[Stories by Fabio Ronca on Medium]]></description>
        <link>https://medium.com/@fabioronca?source=rss-7b6551f4aa49------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oi562GmNWAg0ZbcVjYKdCw.png</url>
            <title>Stories by Fabio Ronca on Medium</title>
            <link>https://medium.com/@fabioronca?source=rss-7b6551f4aa49------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:26:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fabioronca/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[Kubernetes Pills: #003 Kubernetes Architecture]]></title>
            <link>https://medium.com/@fabioronca/kubernetes-pills-003-kubernetes-architecture-8bc6fb085895?source=rss-7b6551f4aa49------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bc6fb085895</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Fabio Ronca]]></dc:creator>
            <pubDate>Sat, 03 Jun 2023 17:57:58 GMT</pubDate>
            <atom:updated>2023-06-03T17:57:58.085Z</atom:updated>
            <content:encoded><![CDATA[<p>In this post, we will speak about the architecture of the Kubernetes system.<br>The picture below, highlights the main components in a Kubernetes system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kY3jnleMSgg37tyVbRPGOA.jpeg" /></figure><p>A deployment of Kubernetes is called a <strong><em>“cluster”.</em></strong></p><h4>Kubernetes Control Plane</h4><p>On the left side of this picture is the <strong><em>control plane</em></strong>, which makes decisions about the cluster and detects and responds to events in the cluster.<br>An example of a decision made by the control plane is scheduling of workloads. An example of responding to an event is creating new resources when an application is deployed.<br>The control plane consists of several components.<br>First is the <strong><em>Kubernetes API server</em></strong>, which exposes the <em>Kubernetes API</em>.<br>All communication in the cluster utilizes this API. For example, the Kubernetes API server accepts commands to view or change the state of the cluster.<br>Next is <strong><em>“etcd”,</em></strong> a highly available key value store that contains all the cluster data. When you tell Kubernetes to deploy your application, that deployment configuration is stored in etcd. Etcd is thus the source of truth for the state in a Kubernetes cluster, and the system works to bring the cluster state into line with what is stored in etcd.<br>The <strong><em>Kubernetes scheduler</em></strong> assigns newly created Pods to nodes.<br>This means that the scheduler determines where your workloads should run within the cluster.<br>The <strong><em>Kubernetes controller manager</em></strong> runs all the controller processes that monitor the cluster state and ensure that the actual state of a cluster matches the desired state.<br>Finally, the <strong><em>cloud controller manager</em></strong> runs controllers that interact with the underlying cloud providers. These controllers effectively link clusters into a cloud provider’s API. Since Kubernetes is open source software and would ideally be adopted by a variety of cloud providers and organizations, it strives to be as cloud-agnostic as possible. The cloud controller manager enables both Kubernetes and the cloud providers to evolve freely without introducing dependencies on the other.</p><h4>Kubernetes Nodes</h4><p>Let’s now zoom in on the right side to see more about the <strong><em>worker nodes</em></strong>.<br>Nodes are the worker machines in a Kubernetes cluster. In other words, user applications are run on nodes. Nodes can be virtual or physical machines. Each node is managed by the control plane and is able to run Pods. Nodes are not created by Kubernetes itself, but rather by the cloud provider. This enables Kubernetes to run on a variety of infrastructures.<br>The components on a node enable that node to run Pods.<br>First is the <strong><em>“kubelet”</em></strong> the most important component. This controller communicates with the Kubernetes API server to receive new and modified Pod specifications and ensure that those Pods and their associated containers are running as desired.<br>The kubelet also reports to the control plane on health and status.<br>In order to start a Pod, the kubelet uses the container runtime.<br>The container runtime is responsible for downloading images and running containers.<br>Rather than providing a single container runtime, Kubernetes implements a Container Runtime Interface that permits pluggability of the container runtime. While <em>Docker</em> is likely the best-known runtime, <em>rkt</em> and <em>CRI-O</em> are two other commonly used container runtimes.<br>Lastly, the <strong><em>Kubernetes proxy</em></strong> is a network proxy that runs on each node in a cluster. This proxy maintains network rules that allow communication to Pods running on nodes. This communication can come from within or outside of the cluster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bc6fb085895" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Pills: #002 Service Type]]></title>
            <link>https://medium.com/@fabioronca/kubernetes-pills-002-service-type-23bc8c712130?source=rss-7b6551f4aa49------2</link>
            <guid isPermaLink="false">https://medium.com/p/23bc8c712130</guid>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[kubernetes-service]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Fabio Ronca]]></dc:creator>
            <pubDate>Thu, 01 Jun 2023 19:47:57 GMT</pubDate>
            <atom:updated>2023-06-01T19:47:57.353Z</atom:updated>
            <content:encoded><![CDATA[<p>In the previous <a href="https://medium.com/p/ac448c965ed9">post</a>, we introduced the Kubernetes Service resource. In this post let’s to describe the different types of Services based on the access scope.</p><p>While defining a Service, we can also choose its access scope. We can decide whether the Service:</p><ul><li>Is only accessible within the cluster.</li><li>Is accessible from within the cluster and the external world.</li><li>Maps to an entity which resides either inside or outside the cluster.</li></ul><p>Access scope is decided by <strong>ServiceType</strong> property, defined when creating the Service.</p><h3>ClusterIP and NodePort</h3><p><strong>ClusterIP</strong> is the default <a href="https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types"><em>ServiceType</em></a>. A Service receives a Virtual IP address, known as its ClusterIP. This Virtual IP address is used for communicating with the Service and is accessible only from within the cluster.</p><p>With the <a href="https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport"><strong>NodePort</strong></a> <em>ServiceType</em>, in addition to a ClusterIP, a high-port, dynamically picked from the default range <strong>30000–32767</strong>, is mapped to the respective Service, from all the worker nodes. For example, if the mapped NodePort is <strong>32233</strong> for the service <strong><em>frontend-svc</em></strong>, then, if we connect to any worker node on port <strong><em>32233</em></strong>, the node would redirect all the traffic to the assigned ClusterIP — <strong>172.17.0.4</strong>. If we prefer a specific high-port number instead, then we can assign that high-port number to the NodePort from the default range when creating the Service.</p><figure><img alt="NodePort" src="https://cdn-images-1.medium.com/max/1024/1*g5YzqiLFqjY9f-yim6VhQw.jpeg" /></figure><p>The <strong>NodePort </strong><em>ServiceType</em> is useful when we want to make our Services accessible from the external world. The end-user connects to any worker node on the specified high-port, which proxies the request internally to the ClusterIP of the Service, then the request is forwarded to the applications running inside the cluster. Let’s not forget that the Service is load balancing such requests, and only forwards the request to one of the Pods running the desired application. To manage access to multiple application Services from the external world, administrators can configure a reverse proxy — an ingress, and define rules that target specific Services within the cluster.</p><h3>LoadBalancer</h3><p>With the <strong><em>LoadBalancer</em></strong> <em>ServiceType</em>:</p><ul><li>NodePort and ClusterIP are automatically created, and the external load balancer will route to them.</li><li>The Service is exposed at a static port on each worker node.</li><li>The Service is exposed externally using the underlying cloud provider’s load balancer feature.</li></ul><figure><img alt="LoadBalancer" src="https://cdn-images-1.medium.com/max/1000/1*pWk7J-pvywTdd055pF7C1Q.jpeg" /></figure><p>The <strong><em>LoadBalancer</em></strong> <em>ServiceType</em> will only work if the underlying infrastructure supports the automatic creation of Load Balancers and have the respective support in Kubernetes, as is the case with the Google Cloud Platform and AWS. If no such feature is configured, the LoadBalancer IP address field is not populated, it remains in Pending state, but the Service will still work as a typical NodePort type Service.</p><h3>ExternalIP</h3><p>A Service can be mapped to an <strong><em>ExternalIP</em></strong> address if it can route to one or more of the worker nodes. Traffic that is ingressed into the cluster with the ExternalIP (as destination IP) on the Service port, gets routed to one of the Service endpoints. This type of service requires an external cloud provider such as Google Cloud Platform or AWS and a Load Balancer configured on the cloud provider’s infrastructure.</p><figure><img alt="ExternalIP" src="https://cdn-images-1.medium.com/max/1000/1*b7N-GNjJN_u30-D068dD5A.jpeg" /></figure><p>Please note that ExternalIPs are not managed by Kubernetes. The cluster administrator has to configure the routing which maps the ExternalIP address to one of the nodes.</p><h3>ExternalName</h3><p><strong><em>ExternalName</em></strong> is a special <em>ServiceType</em> that has no Selectors and does not define any endpoints. When accessed within the cluster, it returns a <strong><em>CNAME</em> </strong>record of an externally configured Service.</p><p>The primary use case of this <em>ServiceType</em> is to make externally configured Services like <strong>my-database.example.com</strong> available to applications inside the cluster. If the externally defined Service resides within the same Namespace, using just the name <strong>my-database</strong> would make it available to other applications and Services within that same Namespace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23bc8c712130" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Pills #001: Services]]></title>
            <link>https://medium.com/@fabioronca/kubernetes-pills-001-services-ac448c965ed9?source=rss-7b6551f4aa49------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac448c965ed9</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[pills]]></category>
            <category><![CDATA[services]]></category>
            <category><![CDATA[k8s]]></category>
            <dc:creator><![CDATA[Fabio Ronca]]></dc:creator>
            <pubDate>Sun, 28 May 2023 17:21:18 GMT</pubDate>
            <atom:updated>2023-05-28T17:55:20.138Z</atom:updated>
            <content:encoded><![CDATA[<p>To access the application, a user or another application need to connect to the Pods. As Pods are ephemeral in nature, resources like IP addresses allocated to them cannot be static. Pods could be terminated abruptly or be rescheduled based on existing requirements.</p><p>Let’s take, for example, a scenario where an operator manages a set of Pods and a client is accessing the Pods directly by using their individual IP addresses.</p><figure><img alt="A Scenario Where a User Is Accessing Pods via their IP Addresses" src="https://cdn-images-1.medium.com/max/1000/1*Kj9jFPCwL6JLdHhMHkNOMw.jpeg" /></figure><p>Unexpectedly, one of the Pods the client is accessing is terminated, and a new Pod is created by the controller. The new Pod will have a new IP address that will not be immediately known by the client.</p><figure><img alt="A New Pod Is Created After an Old One Terminated Unexpectedly" src="https://cdn-images-1.medium.com/max/1024/1*i72txbQfaL7SNvklqncS3Q.jpeg" /></figure><p>To overcome this situation, Kubernetes provides a higher-level abstraction called <strong><em>Service</em></strong>, which logically groups Pods and defines a policy to access them. This grouping is achieved via <strong><em>Labels</em></strong> and <strong><em>Selectors</em></strong>.</p><p>Labels and Selectors use a <strong><em>key-value</em></strong> pair format. In the following picture, <strong><em>app</em></strong> is the Label <strong><em>key</em></strong>, <strong><em>frontend</em></strong> and <strong><em>db</em></strong> are Label <strong><em>values</em></strong> for different Pods.</p><figure><img alt="Grouping of Pods using Labels and Selectors" src="https://cdn-images-1.medium.com/max/1024/1*8votcVBxdwUxK64We2Zx3g.jpeg" /></figure><p>Using the selectors <strong>app==frontend</strong> and <strong>app==db</strong>, we group Pods into two logical sets: one set with 3 Pods, and one set with a single Pod.</p><p>We assign a name to the logical grouping, referred to as a <strong><em>Service</em></strong>. The Service name is also registered with the cluster’s internal DNS service. In our example, we create two Services, <strong><em>frontend-svc</em></strong>, and <strong><em>db-svc</em></strong>, and they have the <strong><em>app==frontend</em></strong> and the <strong><em>app==db</em></strong> Selectors, respectively.</p><p>Services can expose single Pods, ReplicaSets, Deployments, DaemonSets, and StatefulSets. When exposing the Pods managed by an operator, the Service’s Selector may use the same label(s) as the operator.</p><p>The following is an example of a Service object definition:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*X8Nz6qxZwK-Nmrf-Aa4Y-w.png" /></figure><p>In this example, we are creating a <strong><em>frontend-svc</em></strong> Service by selecting all the Pods that have the Label key=a<strong>pp</strong> set to value=<strong>frontend</strong>. By default, each Service receives an IP address routable only inside the cluster, known as <strong><em>ClusterIP</em></strong>. In our example, we have <strong>172.17.0.6</strong> and <strong>172.17.0.9</strong> as ClusterIPs assigned to our <strong><em>frontend-svc</em></strong> and <strong><em>db-svc</em></strong> Services, respectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ReW4m1V6FmFQdEIPQlQ1JQ.jpeg" /></figure><p>The client now connects to a Service via its <strong><em>ClusterIP</em></strong>, which forwards traffic to one of the Pods attached to it. A Service provides load balancing by default while selecting the Pods for traffic forwarding.</p><p>While the Service forwards traffic to Pods, we can select the <strong><em>targetPort</em></strong> on the Pod which receives the traffic. In our example, the <strong><em>frontend-svc</em> </strong>Service receives requests from the client on <strong><em>port:</em></strong><em> </em><strong><em>81</em></strong><em> </em>and then forwards these requests to one of the attached Pods on the <strong><em>targetPort:</em></strong><em> </em><strong><em>8000</em></strong>. If the <strong><em>targetPort</em></strong> is not defined explicitly, then traffic will be forwarded to Pods on the port on which the Service receives traffic. It is very important to ensure that the value of the <strong><em>targetPort </em></strong>matches the value of the <strong><em>containerPort</em></strong> property of the Pod spec section.</p><p>A logical set of a Pod’s IP address, along with the <strong><em>targetPort</em></strong> is referred to as a <strong><em>Service endpoint</em></strong>. In our example, the <strong><em>frontend-svc</em></strong> Service has 3 endpoints: <strong><em>10.0.1.3:8000</em></strong>, <strong><em>10.0.1.4:8000</em></strong>, and <strong><em>10.0.1.5:8000</em></strong>. Endpoints are created and managed automatically by the Service, not by the Kubernetes cluster administrator.</p><p><strong><em>to be continued… stay tuned!</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac448c965ed9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Year, New You: Setting Good Intentions for the Coming Year]]></title>
            <link>https://medium.com/@fabioronca/new-year-new-you-setting-good-intentions-for-the-coming-year-5e4f7b061a5f?source=rss-7b6551f4aa49------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e4f7b061a5f</guid>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[inspiration]]></category>
            <category><![CDATA[new-year]]></category>
            <category><![CDATA[lifestyle]]></category>
            <dc:creator><![CDATA[Fabio Ronca]]></dc:creator>
            <pubDate>Sat, 31 Dec 2022 08:03:08 GMT</pubDate>
            <atom:updated>2022-12-31T08:03:08.926Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QODDsVHC6TagYjGvgSYwbA.jpeg" /></figure><p>The new year is always a time of hope and renewal. It’s an opportunity to leave the past behind and look to the future with optimism. And, most of all, it’s the perfect time to set good intentions for the coming year.</p><p>Good intentions are a way to turn our dreams and ambitions into concrete, achievable goals. They help us focus on what we really want in life and push us to take small steps every day to get closer to our goals.</p><p>If you’re looking for inspiration for your good intentions for the new year, here are some ideas:</p><ol><li>Take care of your health: this can include adopting a healthier lifestyle, such as eating better and getting more exercise, or committing to a sleep hygiene routine.</li><li>Learn something new: this could be a new hobby, a new language, or even just enhancing an existing skill. Learning something new keeps us mentally active and helps us grow personally.</li><li>Volunteer: dedicating time to doing good for others can be extremely rewarding and help put our worries into perspective. Find an organization or project that aligns with your passions and values.</li><li>Strengthen relationships: take the time to connect with the people you care about, whether it’s friends, family, or partners. Dedicate time to building and maintaining these relationships, and you’ll see them become even stronger and more meaningful.</li><li>Make career progress: this could include committing to a new position or acquiring new skills to make a career change. Working towards our professional goals helps us feel satisfied and accomplished.</li></ol><p>No matter what your good intentions for the new year are, the important thing is that they are challenges that excite you and help you grow as a person. Don’t worry if you don’t achieve all of your goals right away: the important thing is to make progress, one step at a time.</p><p>And if you ever feel discouraged or don’t see the results you hoped for, remember that you’re not alone. Ask friends and family for support and encouragement, or seek out online resources to help you stay motivated and on track.</p><p>The new year is a new opportunity to make new experiences, grow, and become the best version of ourselves. With determination and effort, we can achieve any goal we set for ourselves.</p><p>I wish everyone a happy new year full of hope and opportunities!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e4f7b061a5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 YouTube channels for software developers]]></title>
            <link>https://medium.com/@fabioronca/3-youtube-channels-for-software-developers-bb290d0e34e4?source=rss-7b6551f4aa49------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb290d0e34e4</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[beginner-coding]]></category>
            <category><![CDATA[youtube]]></category>
            <category><![CDATA[developer]]></category>
            <dc:creator><![CDATA[Fabio Ronca]]></dc:creator>
            <pubDate>Tue, 27 Dec 2022 16:37:00 GMT</pubDate>
            <atom:updated>2022-12-27T16:37:00.057Z</atom:updated>
            <content:encoded><![CDATA[<p>Here are three YouTube channels that might be interesting for software developers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VPHcZ52la9ddHOezqM8wvw.png" /></figure><p><a href="https://www.youtube.com/@TraversyMedia">Traversy Media</a>: This channel offers a variety of tutorials on technologies like JavaScript, React, Node.js, and more. The creator of the channel, Brad Traversy, is a professional web developer and has a simple and accessible way of explaining complex technical concepts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KgH32hTE8PAPj2QurBUXQg.png" /></figure><p><a href="https://www.youtube.com/@learncodeacademy">LearnCode.academy</a>: This channel offers tutorials and courses on a wide range of programming technologies and languages, such as Python, Java, C++, and more. The tutorials are often very detailed and provide a good overview of key concepts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TNIV39m8Z9HtC13Upde9RA.png" /></figure><p><a href="https://www.youtube.com/@NetNinja">The Net Ninja</a>: This channel primarily focuses on web technologies like React, Angular, and Vue.js, and offers detailed and easy-to-follow tutorials. The creator of the channel, Shaun Pelling, has a very patient and understanding way of explaining technical concepts, which makes him particularly suitable for beginners.</p><p>I hope these channels can be useful to you in your career as a software developer!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb290d0e34e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>