<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on Jakub Žilínek</title>
    <link>https://zilinek.cloud/posts/</link>
    <description>Recent content in Posts on Jakub Žilínek</description>
    <generator>Hugo -- 0.145.0</generator>
    <language>en</language>
    <lastBuildDate>Sun, 16 Mar 2025 12:30:00 +0000</lastBuildDate>
    <atom:link href="https://zilinek.cloud/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Homelab - How I managed to kill my K3S with SQLite</title>
      <link>https://zilinek.cloud/posts/sqlite-issue/</link>
      <pubDate>Sun, 16 Mar 2025 12:30:00 +0000</pubDate>
      <guid>https://zilinek.cloud/posts/sqlite-issue/</guid>
      <description>&lt;h1 id=&#34;how-it-started&#34;&gt;How it started&lt;/h1&gt;
&lt;p&gt;One day I have tried to use my plex instance and it was unreachable. I started digging into it.&lt;/p&gt;
&lt;p&gt;There were couple of containers that wouldn&amp;rsquo;t start and also inspection using &lt;code&gt;k9s&lt;/code&gt; CLI was taking ages.&lt;/p&gt;
&lt;h2 id=&#34;started-digging&#34;&gt;Started digging&lt;/h2&gt;
&lt;p&gt;I have started looking into logs, I saw couple of issues related to SQL - like &lt;code&gt;slow queries&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Then I remembered that K3S is using SQLite as default database, which may not be ideal, for long living clusters.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Homelab - My Kubernetes Journey</title>
      <link>https://zilinek.cloud/posts/homelab/</link>
      <pubDate>Sun, 16 Mar 2025 12:00:00 +0000</pubDate>
      <guid>https://zilinek.cloud/posts/homelab/</guid>
      <description>&lt;h2 id=&#34;before-it-started&#34;&gt;Before It Started&amp;hellip;&lt;/h2&gt;
&lt;p&gt;When I began working as a DevOps engineer at Košík.cz, I started using Kubernetes daily for the first time. I quickly realized I had basically no clue how it worked or how to properly manage it. After reading many blogs and exploring Kubernetes for about a year, I noticed much of the setup had been done by my colleagues.&lt;/p&gt;
&lt;p&gt;I decided to buy a &lt;strong&gt;Raspberry Pi 5 8GB&lt;/strong&gt; and start my own homelab where I would set up an entire Kubernetes cluster myself. My goal was to gain fundamental knowledge about core components of cloud computing.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Networking - MetalLB</title>
      <link>https://zilinek.cloud/posts/networking-metallb/</link>
      <pubDate>Sat, 15 Mar 2025 12:00:00 +0000</pubDate>
      <guid>https://zilinek.cloud/posts/networking-metallb/</guid>
      <description>Take a look at K3S and MetalLB</description>
    </item>
    <item>
      <title>Networking - Nginx Ingress Controller</title>
      <link>https://zilinek.cloud/posts/networking-nginx-controllers/</link>
      <pubDate>Sat, 15 Mar 2025 12:00:00 +0000</pubDate>
      <guid>https://zilinek.cloud/posts/networking-nginx-controllers/</guid>
      <description>Nginx Ingress Controller and k8s routing</description>
    </item>
    <item>
      <title>Networking - External DNS &#43; Pihole</title>
      <link>https://zilinek.cloud/posts/networking-external-dns/</link>
      <pubDate>Fri, 14 Mar 2025 12:00:00 +0000</pubDate>
      <guid>https://zilinek.cloud/posts/networking-external-dns/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Disclaimer:&lt;/p&gt;
&lt;p&gt;This is a documentation of how I did networking in my homelab. It is not a tutorial, but rather a collection of notes and links to resources that helped me along the way. I will try to keep it up to date as I learn more about networking and Kubernetes.&lt;/p&gt;&lt;/blockquote&gt;
&lt;h1 id=&#34;external-dns&#34;&gt;External DNS&lt;/h1&gt;
&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;External DNS is a Kubernetes controller that manages DNS records dynamically. It automates the process of creating and updating DNS records in external DNS providers based on the services and ingress resources in your Kubernetes cluster. Source code can be found &lt;a href=&#34;https://github.com/kubernetes-sigs/external-dns&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Networking - HTTPS &#43; Cert Manager</title>
      <link>https://zilinek.cloud/posts/networking-cert-manager/</link>
      <pubDate>Fri, 14 Mar 2025 12:00:00 +0000</pubDate>
      <guid>https://zilinek.cloud/posts/networking-cert-manager/</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Disclaimer:&lt;/p&gt;
&lt;p&gt;This is a documentation of how I did networking in my homelab. It is not a tutorial, but rather a collection of notes and links to resources that helped me along the way. I will try to keep it up to date as I learn more about networking and Kubernetes.&lt;/p&gt;&lt;/blockquote&gt;
&lt;h1 id=&#34;cert-manager&#34;&gt;Cert Manager&lt;/h1&gt;
&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Cert Manager is a Kubernetes controller that automates the management and issuance of TLS certificates from various issuing sources. It can be used to obtain certificates from Let&amp;rsquo;s Encrypt, HashiCorp Vault, Venafi, and other certificate authorities. The main goal of Cert Manager is to simplify the process of obtaining and renewing TLS certificates for your applications running in Kubernetes. The source code of that controller can be found &lt;a href=&#34;https://github.com/cert-manager/cert-manager&#34;&gt;here&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
