<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>kloia Blog</title>
    <link>https://www.kloia.com/blog</link>
    <description>Blogs about Software, Microservice, AWS, DevOps, Test Automation, GenAI and Observability</description>
    <language>en</language>
    <pubDate>Tue, 03 Mar 2026 10:27:12 GMT</pubDate>
    <dc:date>2026-03-03T10:27:12Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>OpenShift vs Harvester: Choosing a VMware Alternative</title>
      <link>https://www.kloia.com/blog/openshift-vs-harvester-choosing-a-vmware-alternative</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/openshift-vs-harvester-choosing-a-vmware-alternative" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/OpenShift%20vs%20Harvester.png" alt="OpenShift vs Harvester: Choosing a VMware Alternative " class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="color: #000000;"&gt;As VMware licensing costs continue to rise, many infrastructure teams are rethinking their virtualization strategy. The question we hear more often now isn’t “Should we modernize?” but rather “What should we modernize to?”&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #000000;"&gt;Kubernetes-native platforms are quickly becoming the default answer. Instead of running separate stacks for virtual machines and containers, organizations are looking for solutions that can handle both, ideally under a single control plane.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #000000;"&gt;Two names that frequently come up in this conversation are &lt;span style="font-size: 24px;"&gt;&lt;a href="https://harvesterhci.io/"&gt;SUSE Harvester&lt;/a&gt;&lt;/span&gt; and &lt;span style="font-size: 20px;"&gt;&lt;a href="https://www.redhat.com/en/technologies/cloud-computing/openshift"&gt;Red Hat OpenShift.&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #000000;"&gt;Both promise modern, Kubernetes-based virtualization. Both can replace traditional hypervisors in on-prem environments. But once you look closer, their design philosophies, and the experience they offer,&amp;nbsp; are quite different.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #000000;"&gt;Here’s what stands out after evaluating both platforms in real-world scenarios.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/openshift-vs-harvester-choosing-a-vmware-alternative" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/OpenShift%20vs%20Harvester.png" alt="OpenShift vs Harvester: Choosing a VMware Alternative " class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="color: #000000;"&gt;As VMware licensing costs continue to rise, many infrastructure teams are rethinking their virtualization strategy. The question we hear more often now isn’t “Should we modernize?” but rather “What should we modernize to?”&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #000000;"&gt;Kubernetes-native platforms are quickly becoming the default answer. Instead of running separate stacks for virtual machines and containers, organizations are looking for solutions that can handle both, ideally under a single control plane.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #000000;"&gt;Two names that frequently come up in this conversation are &lt;span style="font-size: 24px;"&gt;&lt;a href="https://harvesterhci.io/"&gt;SUSE Harvester&lt;/a&gt;&lt;/span&gt; and &lt;span style="font-size: 20px;"&gt;&lt;a href="https://www.redhat.com/en/technologies/cloud-computing/openshift"&gt;Red Hat OpenShift.&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #000000;"&gt;Both promise modern, Kubernetes-based virtualization. Both can replace traditional hypervisors in on-prem environments. But once you look closer, their design philosophies, and the experience they offer,&amp;nbsp; are quite different.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;span style="color: #000000;"&gt;Here’s what stands out after evaluating both platforms in real-world scenarios.&lt;/span&gt;&lt;br&gt;&lt;br&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Fopenshift-vs-harvester-choosing-a-vmware-alternative&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>DevOps</category>
      <category>CloudNative</category>
      <category>On-Prem Infrastructure</category>
      <category>suse harvester</category>
      <category>VMware Alternatives</category>
      <category>Kubernetes Virtualization</category>
      <category>redhat openshift</category>
      <pubDate>Tue, 10 Feb 2026 14:29:58 GMT</pubDate>
      <author>omer.urhan@kloia.com (Omer Faruk Urhan)</author>
      <guid>https://www.kloia.com/blog/openshift-vs-harvester-choosing-a-vmware-alternative</guid>
      <dc:date>2026-02-10T14:29:58Z</dc:date>
    </item>
    <item>
      <title>AWS GenAI Transform SQL Performance &amp; Use Cases | Kloia Blog</title>
      <link>https://www.kloia.com/blog/our-experience-with-aws-transform-sql-using-genai</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/our-experience-with-aws-transform-sql-using-genai" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/Our%20Experience%20with%20AWS%20Transform%20SQL%20Using%20GenAI-2.png" alt="AWS GenAI Transform SQL Performance &amp;amp; Use Cases | Kloia Blog" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;After years of manually wrestling with MSSQL to PostgreSQL conversions using SCT and DMS, I finally got my hands on AWS Transform SQL. I put it through its paces on a production-scale database with 1,500+ stored procedures. The results? Surprisingly impressive - and a few gotchas worth knowing about.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/our-experience-with-aws-transform-sql-using-genai" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/Our%20Experience%20with%20AWS%20Transform%20SQL%20Using%20GenAI-2.png" alt="AWS GenAI Transform SQL Performance &amp;amp; Use Cases | Kloia Blog" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;After years of manually wrestling with MSSQL to PostgreSQL conversions using SCT and DMS, I finally got my hands on AWS Transform SQL. I put it through its paces on a production-scale database with 1,500+ stored procedures. The results? Surprisingly impressive - and a few gotchas worth knowing about.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Four-experience-with-aws-transform-sql-using-genai&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>AWS</category>
      <category>Software</category>
      <category>genai</category>
      <category>DatabaseMigration</category>
      <category>MSSQL</category>
      <category>SCT</category>
      <category>DMS</category>
      <category>AuroraPostgreSQL</category>
      <category>PostgreSQL</category>
      <category>CloudMigration</category>
      <pubDate>Thu, 08 Jan 2026 20:45:18 GMT</pubDate>
      <author>tarik@kloia.com (Tarık Guven)</author>
      <guid>https://www.kloia.com/blog/our-experience-with-aws-transform-sql-using-genai</guid>
      <dc:date>2026-01-08T20:45:18Z</dc:date>
    </item>
    <item>
      <title>KubeVirt on Amazon EKS for Containers and VMs | Kubernetes</title>
      <link>https://www.kloia.com/blog/kubevirt-on-amazon-eks-unifying-containers-and-vms-in-kubernetes</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/kubevirt-on-amazon-eks-unifying-containers-and-vms-in-kubernetes" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/KubeVirt%20on%20AWS%20EKS_%20Unifying%20Containers%20and%20VMs%20in%20Kubernetes%20(2).png" alt="KubeVirt on Amazon EKS for Containers and VMs | Kubernetes" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;Kubernetes is the de facto standard for container orchestration, enabling developers to easily deploy, scale, and manage containerized applications. However, there are scenarios where running virtual machines (VMs) alongside containers is necessary. This is where KubeVirt comes into play.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;KubeVirt is a Kubernetes extension that allows you to manage VMs alongside containers within the same Kubernetes cluster. This blog post will guide you through the process of installing KubeVirt on an Amazon Elastic Kubernetes Service (EKS) cluster, complete with examples and best practices.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/kubevirt-on-amazon-eks-unifying-containers-and-vms-in-kubernetes" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/KubeVirt%20on%20AWS%20EKS_%20Unifying%20Containers%20and%20VMs%20in%20Kubernetes%20(2).png" alt="KubeVirt on Amazon EKS for Containers and VMs | Kubernetes" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;Kubernetes is the de facto standard for container orchestration, enabling developers to easily deploy, scale, and manage containerized applications. However, there are scenarios where running virtual machines (VMs) alongside containers is necessary. This is where KubeVirt comes into play.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;KubeVirt is a Kubernetes extension that allows you to manage VMs alongside containers within the same Kubernetes cluster. This blog post will guide you through the process of installing KubeVirt on an Amazon Elastic Kubernetes Service (EKS) cluster, complete with examples and best practices.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Fkubevirt-on-amazon-eks-unifying-containers-and-vms-in-kubernetes&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>AWS</category>
      <category>DevOps</category>
      <category>Kubernetes</category>
      <category>EKS</category>
      <category>Containers</category>
      <category>KubeVirt</category>
      <pubDate>Thu, 25 Dec 2025 10:00:00 GMT</pubDate>
      <author>ahmet.aydin@kloia.com (Ahmet Aydın)</author>
      <guid>https://www.kloia.com/blog/kubevirt-on-amazon-eks-unifying-containers-and-vms-in-kubernetes</guid>
      <dc:date>2025-12-25T10:00:00Z</dc:date>
    </item>
    <item>
      <title>Java Virtual Threads Benchmark &amp; Performance Analysis | Kloia</title>
      <link>https://www.kloia.com/blog/benchmarking-java-virtual-threads-a-comprehensive-analysis</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/benchmarking-java-virtual-threads-a-comprehensive-analysis" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/benchmarking_java_virtual_threads_a_comprehensive_analysis_blog.webp" alt="Java Virtual Threads Benchmark &amp;amp; Performance Analysis | Kloia" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A groundbreaking innovation called Java Virtual Threads (Project Loom) was designed to improve the concurrency mechanism and boost Java application performance. Since virtual threads are more lightweight than traditional threads, a larger number of concurrent threads can be managed more effectively.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/benchmarking-java-virtual-threads-a-comprehensive-analysis" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/benchmarking_java_virtual_threads_a_comprehensive_analysis_blog.webp" alt="Java Virtual Threads Benchmark &amp;amp; Performance Analysis | Kloia" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;A groundbreaking innovation called Java Virtual Threads (Project Loom) was designed to improve the concurrency mechanism and boost Java application performance. Since virtual threads are more lightweight than traditional threads, a larger number of concurrent threads can be managed more effectively.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Fbenchmarking-java-virtual-threads-a-comprehensive-analysis&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>java</category>
      <category>performance</category>
      <category>Software</category>
      <category>benchmarking</category>
      <category>Resource Utilization</category>
      <category>Scalability</category>
      <category>java virtual threads</category>
      <category>Project Loom</category>
      <pubDate>Fri, 19 Dec 2025 12:00:00 GMT</pubDate>
      <guid>https://www.kloia.com/blog/benchmarking-java-virtual-threads-a-comprehensive-analysis</guid>
      <dc:date>2025-12-19T12:00:00Z</dc:date>
      <dc:creator>Baran Gayretli</dc:creator>
    </item>
    <item>
      <title>Werner Vogels' Final re:Invent Keynote: The Renaissance Developer</title>
      <link>https://www.kloia.com/blog/werner-vogels-final-reinvent-keynote-the-renaissance-developer</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/werner-vogels-final-reinvent-keynote-the-renaissance-developer" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/Werner-reinvent2025-renaissancedeveloper-1.png" alt="Werner Vogels' Final re:Invent Keynote: The Renaissance Developer" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Werner’s keynotes have always been inspiring rather than sales&amp;amp;marketing, which is why his sessions are consistently the most anticipated at every re:Invent. Attendees usually known to return back homes&amp;nbsp;after his keynote, even if there’s still another day of the conference left.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/werner-vogels-final-reinvent-keynote-the-renaissance-developer" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/Werner-reinvent2025-renaissancedeveloper-1.png" alt="Werner Vogels' Final re:Invent Keynote: The Renaissance Developer" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Werner’s keynotes have always been inspiring rather than sales&amp;amp;marketing, which is why his sessions are consistently the most anticipated at every re:Invent. Attendees usually known to return back homes&amp;nbsp;after his keynote, even if there’s still another day of the conference left.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Fwerner-vogels-final-reinvent-keynote-the-renaissance-developer&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>AWS</category>
      <category>reinvent2025</category>
      <pubDate>Mon, 08 Dec 2025 02:58:15 GMT</pubDate>
      <author>derya@kloia.com (Derya (Dorian) Sezen)</author>
      <guid>https://www.kloia.com/blog/werner-vogels-final-reinvent-keynote-the-renaissance-developer</guid>
      <dc:date>2025-12-08T02:58:15Z</dc:date>
    </item>
    <item>
      <title>Kubernetes 1.34: Fine-Grained Container Restart Policies</title>
      <link>https://www.kloia.com/blog/kubernetes-1-34-fine-grained-container-restart-policies</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/kubernetes-1-34-fine-grained-container-restart-policies" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/Kubernetes%201.34_%20Fine-Grained%20Container%20Restart%20Policies-1.png" alt="Kubernetes 1.34: Fine-Grained Container Restart Policies" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Every Kubernetes user has faced the difficulty of managing Pods with multiple containers. Modern Pods often have a main application container, a sidecar container for extra tasks (like monitoring or managing secrets), and an init container for a one-time initial process. However, all these containers were tied to the same restart rule for the whole Pod, which was often frustrating.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/kubernetes-1-34-fine-grained-container-restart-policies" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/Kubernetes%201.34_%20Fine-Grained%20Container%20Restart%20Policies-1.png" alt="Kubernetes 1.34: Fine-Grained Container Restart Policies" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Every Kubernetes user has faced the difficulty of managing Pods with multiple containers. Modern Pods often have a main application container, a sidecar container for extra tasks (like monitoring or managing secrets), and an init container for a one-time initial process. However, all these containers were tied to the same restart rule for the whole Pod, which was often frustrating.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Fkubernetes-1-34-fine-grained-container-restart-policies&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>DevOps</category>
      <category>Kubernetes</category>
      <category>Containers</category>
      <category>Cloud Computing</category>
      <category>CloudNative</category>
      <category>PodManagement</category>
      <category>K8s134</category>
      <pubDate>Tue, 30 Sep 2025 14:53:02 GMT</pubDate>
      <author>raja.haikal@kloia.com (Raja Haikal)</author>
      <guid>https://www.kloia.com/blog/kubernetes-1-34-fine-grained-container-restart-policies</guid>
      <dc:date>2025-09-30T14:53:02Z</dc:date>
    </item>
    <item>
      <title>AWS Cloud Cost Savings by Migrating Kubernetes Workloads to Graviton</title>
      <link>https://www.kloia.com/blog/aws-cloud-cost-savings-by-migrating-kubernetes-workloads-to-graviton</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/aws-cloud-cost-savings-by-migrating-kubernetes-workloads-to-graviton" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/AWS%20Cloud%20Cost%20Savings%20by%20Migrating%20Kubernetes%20Workloads%20to%20Graviton-1.png" alt="AWS Cloud Cost Savings by Migrating Kubernetes Workloads to Graviton" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Running Kubernetes clusters on AWS Cloud is powerful and offers various deployment options depending on instance choice. One significant opportunity for optimization is migrating workloads from the traditional AMD64 (x86_64) architecture to AWS ARM64 Graviton instances. This post walks through our recent migration project, highlights the practical steps and real-world challenges.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/aws-cloud-cost-savings-by-migrating-kubernetes-workloads-to-graviton" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/AWS%20Cloud%20Cost%20Savings%20by%20Migrating%20Kubernetes%20Workloads%20to%20Graviton-1.png" alt="AWS Cloud Cost Savings by Migrating Kubernetes Workloads to Graviton" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Running Kubernetes clusters on AWS Cloud is powerful and offers various deployment options depending on instance choice. One significant opportunity for optimization is migrating workloads from the traditional AMD64 (x86_64) architecture to AWS ARM64 Graviton instances. This post walks through our recent migration project, highlights the practical steps and real-world challenges.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Faws-cloud-cost-savings-by-migrating-kubernetes-workloads-to-graviton&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>AWS</category>
      <category>DevOps</category>
      <category>Kubernetes</category>
      <category>CloudNative</category>
      <category>CloudCostOptimization</category>
      <category>FinOps</category>
      <category>ARM64</category>
      <pubDate>Tue, 09 Sep 2025 10:11:32 GMT</pubDate>
      <author>muhammad.bahy@kloia.com (Muhammad Bintang Bahy)</author>
      <guid>https://www.kloia.com/blog/aws-cloud-cost-savings-by-migrating-kubernetes-workloads-to-graviton</guid>
      <dc:date>2025-09-09T10:11:32Z</dc:date>
    </item>
    <item>
      <title>AWS EKS Multi-Tenancy Guide with vCluster</title>
      <link>https://www.kloia.com/blog/aws-eks-multi-tenancy-with-vcluster</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/aws-eks-multi-tenancy-with-vcluster" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/AWS%20EKS%20Multi-Tenancy%E2%80%A8with%20vCluster-1.png.png" alt="AWS EKS Multi-Tenancy Guide with vCluster" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Kubernetes is the de facto standard for container orchestration, allowing teams to deploy, scale, and manage containerized applications. However, implementing multi-tenancy in Kubernetes is not always straightforward. Many organizations need to run multiple environments such as development, staging, and production on the same infrastructure while keeping each tenant isolated in terms of resources, security, and access.&lt;br&gt;&lt;br&gt;The challenge becomes even greater as the number of environments grows. Creating a separate Kubernetes cluster for every team or project provides strong isolation but also increases infrastructure costs, operational complexity, and maintenance work. On the other hand, relying only on namespaces to achieve multi-tenancy can save money but often fails to provide complete isolation, custom configurations, or flexibility in Kubernetes versions.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/aws-eks-multi-tenancy-with-vcluster" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/AWS%20EKS%20Multi-Tenancy%E2%80%A8with%20vCluster-1.png.png" alt="AWS EKS Multi-Tenancy Guide with vCluster" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Kubernetes is the de facto standard for container orchestration, allowing teams to deploy, scale, and manage containerized applications. However, implementing multi-tenancy in Kubernetes is not always straightforward. Many organizations need to run multiple environments such as development, staging, and production on the same infrastructure while keeping each tenant isolated in terms of resources, security, and access.&lt;br&gt;&lt;br&gt;The challenge becomes even greater as the number of environments grows. Creating a separate Kubernetes cluster for every team or project provides strong isolation but also increases infrastructure costs, operational complexity, and maintenance work. On the other hand, relying only on namespaces to achieve multi-tenancy can save money but often fails to provide complete isolation, custom configurations, or flexibility in Kubernetes versions.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Faws-eks-multi-tenancy-with-vcluster&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>AWS</category>
      <category>DevOps</category>
      <category>Cloud</category>
      <category>Kubernetes</category>
      <category>k8s</category>
      <category>EKS</category>
      <category>CloudNative</category>
      <category>PlatformEngineering</category>
      <category>vCluster</category>
      <pubDate>Thu, 21 Aug 2025 09:30:56 GMT</pubDate>
      <author>raja.haikal@kloia.com (Raja Haikal)</author>
      <guid>https://www.kloia.com/blog/aws-eks-multi-tenancy-with-vcluster</guid>
      <dc:date>2025-08-21T09:30:56Z</dc:date>
    </item>
    <item>
      <title>Kubernetes in the cloud: AKS vs EKS</title>
      <link>https://www.kloia.com/blog/kubernetes-in-the-cloud-aks-vs-eks</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/kubernetes-in-the-cloud-aks-vs-eks" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/kubernetes_in_the_cloud_aks_vs_eks.webp" alt="Kubernetes in the cloud: AKS vs EKS" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span&gt;AWS EKS and Azure AKS are two major managed Kubernetes Services&lt;/span&gt;. As organizations continue their cloud transformation journeys, these platforms serve as the foundation for countless enterprise workloads worldwide. While both cloud providers offer wide service portfolios, their managed Kubernetes offerings have become critical for modern applications.&lt;br&gt;&lt;br&gt;Whether you are an Azure or AWS customer, or simply evaluating your options for managed Kubernetes, this blogpost aims to show how those providers approach aspects like version management, networking, and other key differences between the two cloud platforms.&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/kubernetes-in-the-cloud-aks-vs-eks" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/kubernetes_in_the_cloud_aks_vs_eks.webp" alt="Kubernetes in the cloud: AKS vs EKS" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span&gt;AWS EKS and Azure AKS are two major managed Kubernetes Services&lt;/span&gt;. As organizations continue their cloud transformation journeys, these platforms serve as the foundation for countless enterprise workloads worldwide. While both cloud providers offer wide service portfolios, their managed Kubernetes offerings have become critical for modern applications.&lt;br&gt;&lt;br&gt;Whether you are an Azure or AWS customer, or simply evaluating your options for managed Kubernetes, this blogpost aims to show how those providers approach aspects like version management, networking, and other key differences between the two cloud platforms.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Fkubernetes-in-the-cloud-aks-vs-eks&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>AWS</category>
      <category>DevOps</category>
      <category>Kubernetes</category>
      <category>k8s</category>
      <category>EKS</category>
      <category>Cloud Computing</category>
      <category>KubernetesDevelopment</category>
      <category>Kubernetes Support</category>
      <category>AKS</category>
      <category>Cloud Transformation</category>
      <pubDate>Mon, 30 Jun 2025 21:39:08 GMT</pubDate>
      <author>doga.akcinar@kloia.com (Doga Akçınar)</author>
      <guid>https://www.kloia.com/blog/kubernetes-in-the-cloud-aks-vs-eks</guid>
      <dc:date>2025-06-30T21:39:08Z</dc:date>
    </item>
    <item>
      <title>Understanding Load Balancing Across OSI Layers: Layer 3, Layer 4, and Layer 7</title>
      <link>https://www.kloia.com/blog/understanding-load-balancing-across-osi-layers-layer-3-layer-4-and-layer-7</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/understanding-load-balancing-across-osi-layers-layer-3-layer-4-and-layer-7" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/Load%20Balancing%20Across%20OSI%20Layers_%20Layer%203%2c%20Layer%204%2c%20and%20Layer%207-1.png" alt="Understanding Load Balancing Across OSI Layers: Layer 3, Layer 4, and Layer 7" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="font-size: 20px; color: #444746;"&gt;Load balancing, a critical component in managing network traffic, plays a vital role in maintaining network reliability. Load balancing offers different methods and advantages that align with specific enterprise needs.&lt;/span&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://www.kloia.com/blog/understanding-load-balancing-across-osi-layers-layer-3-layer-4-and-layer-7" title="" class="hs-featured-image-link"&gt; &lt;img src="https://www.kloia.com/hubfs/Load%20Balancing%20Across%20OSI%20Layers_%20Layer%203%2c%20Layer%204%2c%20and%20Layer%207-1.png" alt="Understanding Load Balancing Across OSI Layers: Layer 3, Layer 4, and Layer 7" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;&lt;span style="font-size: 20px; color: #444746;"&gt;Load balancing, a critical component in managing network traffic, plays a vital role in maintaining network reliability. Load balancing offers different methods and advantages that align with specific enterprise needs.&lt;/span&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4602321&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.kloia.com%2Fblog%2Funderstanding-load-balancing-across-osi-layers-layer-3-layer-4-and-layer-7&amp;amp;bu=https%253A%252F%252Fwww.kloia.com%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>AWS</category>
      <category>Cloud</category>
      <category>Kubernetes</category>
      <category>Cloud Computing</category>
      <category>LoadBalancing</category>
      <category>Cloud Networking</category>
      <category>Data Engineering</category>
      <pubDate>Wed, 18 Jun 2025 08:40:29 GMT</pubDate>
      <author>halil@kloia.com (Halil Bozan)</author>
      <guid>https://www.kloia.com/blog/understanding-load-balancing-across-osi-layers-layer-3-layer-4-and-layer-7</guid>
      <dc:date>2025-06-18T08:40:29Z</dc:date>
    </item>
  </channel>
</rss>
