<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>k3s on jawr</title><link>https://jawr.github.io/jl-lu/tags/k3s/</link><description>Recent content in k3s on jawr</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© {year}</copyright><lastBuildDate>Thu, 04 Mar 2021 09:49:21 +0900</lastBuildDate><atom:link href="https://jawr.github.io/jl-lu/tags/k3s/index.xml" rel="self" type="application/rss+xml"/><item><title>nixos &amp; kubernete woes</title><link>https://jawr.github.io/jl-lu/blog/nixos-and-kubernetes-woes/</link><pubDate>Thu, 04 Mar 2021 09:49:21 +0900</pubDate><guid>https://jawr.github.io/jl-lu/blog/nixos-and-kubernetes-woes/</guid><description>After my recent fiddling with k8s, I decided to try out k3s which offers a slimmed down version of kubernetes. I also decided to take the plunge and push up my virtual experimenting and place it in to the cloud, using the lovely Hetzner nixops plugin .
Routing Hell By far the most frustrating issue I encountered revolved around routing. Inter communication between the nodes is unencrypted by default (when using flannel) and so I wanted to link all nodes and pod via wireguard.</description></item></channel></rss>