<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nixos on jawr</title><link>https://jawr.github.io/jl-lu/tags/nixos/</link><description>Recent content in nixos 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/nixos/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><item><title>nixos - wireguard &amp; modules</title><link>https://jawr.github.io/jl-lu/blog/nixos-wireguard-and-modules/</link><pubDate>Tue, 16 Feb 2021 17:29:58 +0900</pubDate><guid>https://jawr.github.io/jl-lu/blog/nixos-wireguard-and-modules/</guid><description>Refactoring In my previous post I attacked the kubernetes configuration using only one module, the rest created relied on functions.
It didn&amp;rsquo;t feel idiomatic and when trying to add wireguard, the cracks started to appear. It felt like I was fighting with the language.
After some wonderful duck debugging with the excellent community on IRC, I decided to refactor what I had in to modules.
Modules The NixOS wiki has an excellent article on modules, but the gist is that a module is a set that has the following syntax:</description></item><item><title>nixos - starting a kluster</title><link>https://jawr.github.io/jl-lu/blog/nixos-starting-a-kubernetes-cluster/</link><pubDate>Mon, 08 Feb 2021 23:11:33 +0900</pubDate><guid>https://jawr.github.io/jl-lu/blog/nixos-starting-a-kubernetes-cluster/</guid><description>Too many Buzzwords Lately I have been porting a project from a systemd service to a fully fledged, cutting edge, Docker on kubernetes setup.
The main reason for this has been $reason.
Initially I was using minikube which uses VirtualBox to create a ready made cluster which is perfect to learn with.
Searching for a home After doing some research and deciding that a hosted solution was far too expensive for my needs, I started to entertain the idea of running my own cluster and to kubernet all my existing services and projects in to one giant auto healing, auto scaling ball of cool.</description></item><item><title>nixos - cloud-init</title><link>https://jawr.github.io/jl-lu/blog/nixos-cloud-init/</link><pubDate>Fri, 22 Jan 2021 12:55:09 +0900</pubDate><guid>https://jawr.github.io/jl-lu/blog/nixos-cloud-init/</guid><description>But there&amp;rsquo;s no image?! When starting a new instance up on scaleway there is no option to select NixOS, but using the cloud init hook you are able to boot up an instance.
After a few moments you can login using your predefined SSH keys which have been initialised, along with the hostname and SSH serrvice, in /etc/nixos/configuration.nix:
{ ... }: { imports = [ ./hardware-configuration.nix ./host.nix ]; boot.cleanTmpDir = true; networking.</description></item></channel></rss>