<?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>Forem:  Jorge Lozano</title>
    <description>The latest articles on Forem by  Jorge Lozano (@jorge_humbertolozanoare).</description>
    <link>https://forem.com/jorge_humbertolozanoare</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%2F3080399%2F7470064f-9be8-4556-b6b5-d772a4c956b9.png</url>
      <title>Forem:  Jorge Lozano</title>
      <link>https://forem.com/jorge_humbertolozanoare</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/jorge_humbertolozanoare"/>
    <language>en</language>
    <item>
      <title>Mastering Chaos: How To Built a Chaos Engineering Operator in Go for Kubernetes</title>
      <dc:creator> Jorge Lozano</dc:creator>
      <pubDate>Mon, 13 Oct 2025 03:11:55 +0000</pubDate>
      <link>https://forem.com/jorge_humbertolozanoare/mastering-chaos-how-to-built-a-chaos-engineering-operator-in-go-for-kubernetes-4lpc</link>
      <guid>https://forem.com/jorge_humbertolozanoare/mastering-chaos-how-to-built-a-chaos-engineering-operator-in-go-for-kubernetes-4lpc</guid>
      <description>&lt;p&gt;How confident are you that your Kubernetes applications can withstand production turbulence? To turn that confidence into certainty, I built a new Chaos Engineering Operator in Go.&lt;br&gt;
This tool provides a declarative, safe, and automated way to inject faults and proactively validate the resilience of your infrastructure.&lt;br&gt;
In my latest article, I explore the architecture behind my operator and how you can adopt Chaos Engineering as a core practice to build truly unbreakable systems.&lt;br&gt;
Discover how right here and get ready for the alpha release!&lt;/p&gt;

&lt;p&gt;👉 Read the full article:&lt;br&gt;
&lt;a href="https://medium.com/@jlozanoa6/mastering-chaos-how-to-built-a-chaos-engineering-operator-in-go-for-kubernetes-e352db74bb7d" rel="noopener noreferrer"&gt;https://medium.com/@jlozanoa6/mastering-chaos-how-to-built-a-chaos-engineering-operator-in-go-for-kubernetes-e352db74bb7d&lt;/a&gt;&lt;/p&gt;

</description>
      <category>kubernetes</category>
      <category>cloudcomputing</category>
      <category>devops</category>
      <category>softwareengineering</category>
    </item>
    <item>
      <title>Building a Resilient EKS Disaster Recovery Plan (DRP) on AWS</title>
      <dc:creator> Jorge Lozano</dc:creator>
      <pubDate>Wed, 23 Apr 2025 16:52:52 +0000</pubDate>
      <link>https://forem.com/jorge_humbertolozanoare/building-a-resilient-eks-disaster-recovery-plan-drp-on-aws-c85</link>
      <guid>https://forem.com/jorge_humbertolozanoare/building-a-resilient-eks-disaster-recovery-plan-drp-on-aws-c85</guid>
      <description>&lt;p&gt;AWS EKS is a powerful solution, but building a solid Disaster Recovery Plan (DRP) for it can be complex.&lt;/p&gt;

&lt;p&gt;In this article, I walk through how to design a resilient EKS architecture on AWS, including:&lt;br&gt;
✅ Multi-AZ strategies&lt;br&gt;&lt;br&gt;
✅ RTO/RPO planning&lt;br&gt;&lt;br&gt;
✅ Tools like Route 53, AWS Backup&lt;br&gt;&lt;br&gt;
✅ Best practices for production environments&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://medium.com/@jlozanoa6/building-a-resilient-eks-disaster-recovery-plan-drp-on-aws-5883150ce8e7" rel="noopener noreferrer"&gt;Read the full article on Medium&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;Have experience with cloud DR or EKS? Let’s chat in the comments 🚀&lt;/p&gt;

</description>
      <category>aws</category>
      <category>kubernetes</category>
      <category>devops</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
