<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>kubernetes on jawr</title><link>https://jawr.github.io/jl-lu/tags/kubernetes/</link><description>Recent content in kubernetes on jawr</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© {year}</copyright><lastBuildDate>Mon, 08 Feb 2021 23:11:33 +0900</lastBuildDate><atom:link href="https://jawr.github.io/jl-lu/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>