<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microk8s on Samuel Matildes - Knowledge Base</title><link>https://matildes.dev/tags/microk8s/</link><description>Recent content in Microk8s on Samuel Matildes - Knowledge Base</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 26 Oct 2026 12:27:57 +0000</lastBuildDate><atom:link href="https://matildes.dev/tags/microk8s/index.xml" rel="self" type="application/rss+xml"/><item><title>Retiring kube-proxy IPVS on MicroK8s: An Upgrade Readiness Runbook</title><link>https://matildes.dev/kubernetes/microk8s-kube-proxy-ipvs-migration/</link><pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate><guid>https://matildes.dev/kubernetes/microk8s-kube-proxy-ipvs-migration/</guid><description>&lt;p&gt;&lt;i class="fas fa-route" aria-hidden="true"&gt;&lt;/i&gt; A focused runbook for checking whether a MicroK8s cluster needs an IPVS migration before its next Kubernetes minor upgrade.&lt;/p&gt;
&lt;h2 id="scope-and-outcome"&gt;Scope and outcome&lt;a class="td-heading-self-link" href="#scope-and-outcome" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This is not a general CNI replacement guide and it does not change Traefik, IngressRoutes, or application manifests. It covers one question: &lt;strong&gt;does this cluster run kube-proxy in &lt;code&gt;ipvs&lt;/code&gt; mode, and if so, can it move safely to &lt;code&gt;iptables&lt;/code&gt; before the next MicroK8s minor upgrade?&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Self-Host Honcho on Kubernetes with LiteLLM, Redis, and GitHub Copilot</title><link>https://matildes.dev/ai/honcho-litellm-github-copilot/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://matildes.dev/ai/honcho-litellm-github-copilot/</guid><description>&lt;p&gt;&lt;i class="fas fa-brain" aria-hidden="true"&gt;&lt;/i&gt; A self-hosted memory service for Hermes, with LiteLLM as the model gateway and GitHub Copilot as an upstream provider.&lt;/p&gt;
&lt;div class="kb-callout kb-callout--warning"&gt;
 &lt;div class="kb-callout__title"&gt;
 &lt;i class="fas fa-triangle-exclamation" aria-hidden="true"&gt;&lt;/i&gt;
 &lt;span&gt;Illustrative configuration only&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="kb-callout__body"&gt;
 Every hostname, namespace, IP address, image version, model name, key and resource value in this guide is an &lt;strong&gt;example&lt;/strong&gt;. Do not paste it into a production cluster unchanged. Create your own secrets outside Git, verify the current upstream image and model names, and apply your own network, backup and update policies.
 &lt;/div&gt;
&lt;/div&gt;

&lt;h2 id="architecture-at-a-glance"&gt;Architecture at a glance&lt;a class="td-heading-self-link" href="#architecture-at-a-glance" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;figure class="honcho-architecture"&gt;
 &lt;img src="architecture.svg" alt="Diagram showing the relationship between Hermes, Honcho, LiteLLM, Redis, PostgreSQL with pgvector, and LLM endpoints"&gt;
&lt;/figure&gt;
&lt;p&gt;The request path is deliberately split into specialised layers:&lt;/p&gt;</description></item><item><title>MicroK8s with Traefik: Public and Private Application Deployment</title><link>https://matildes.dev/kubernetes/microk8s-simple-implementation/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://matildes.dev/kubernetes/microk8s-simple-implementation/</guid><description>&lt;p&gt;&lt;i class="fas fa-server" aria-hidden="true"&gt;&lt;/i&gt; MicroK8s Home Lab with Traefik Ingress&lt;/p&gt;
&lt;h2 id="summary"&gt;Summary&lt;a class="td-heading-self-link" href="#summary" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This guide walks through setting up a complete MicroK8s cluster on Ubuntu with &lt;strong&gt;Traefik&lt;/strong&gt; as the ingress controller. The architecture supports two types of applications: &lt;strong&gt;public apps&lt;/strong&gt; exposed to the internet via Cloudflare DNS and TLS, and &lt;strong&gt;private apps&lt;/strong&gt; accessible only from the local network. We&amp;rsquo;ll deploy containerized workloads running inside Kubernetes pods, proxy traffic to external hosts, and set up monitoring dashboards—all managed through declarative YAML manifests.&lt;/p&gt;</description></item></channel></rss>