<?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>Homelab on Wolkwacht</title>
    <link>https://wolkwacht.nl/tags/homelab/</link>
    <description>Recent content in Homelab on Wolkwacht</description>
    <image>
      <title>Wolkwacht</title>
      <url>https://wolkwacht.nl/images/branding/feature-image.png</url>
      <link>https://wolkwacht.nl/images/branding/feature-image.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 08 Apr 2019 19:31:14 +0000</lastBuildDate>
    <atom:link href="https://wolkwacht.nl/tags/homelab/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>k3s: Kubernetes Dashboard &#43; load balancer</title>
      <link>https://wolkwacht.nl/posts/k3s-kubernetes-dashboard-load-balancer/</link>
      <pubDate>Mon, 08 Apr 2019 19:31:14 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/k3s-kubernetes-dashboard-load-balancer/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;https://www.jurgenallewijn.nl/k3s-lightweight-kubernetes-distribution-first-experience/&#34;&gt;my post about first experience with k3s&lt;/a&gt; I blogged about setting up my k3s based cluster on Raspberry PI&amp;rsquo;s. Since that post I have added two more nodes Raspberry Pi&amp;rsquo;s and also updated to the &lt;a href=&#34;https://twitter.com/Rancher_Labs/status/1111810281443901450&#34;&gt;0.3.0&lt;/a&gt; version of k3s.&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;pi@k3s-master-1:~ $ kubectl get nodes
NAME           STATUS   ROLES    AGE     VERSION
k3s-master-1   Ready    master   4h11m   v1.13.5-k3s.1
k3s-node-1     Ready    node     129m    v1.13.5-k3s.1
k3s-node-2     Ready    node     118m    v1.13.5-k3s.1
k3s-node-3     Ready    node     119m    v1.13.5-k3s.1
pi@k3s-master-1:~ $
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Next step for me was getting the Kubernetes Dashboard up and running. I used the information from &lt;a href=&#34;https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/&#34;&gt;Web UI (Dashboard)&lt;/a&gt; First downloaded I the kubernetes-dashboard.yaml&lt;/p&gt;</description>
    </item>
    <item>
      <title>k3s: Lightweight Kubernetes Distribution first experience</title>
      <link>https://wolkwacht.nl/posts/k3s-lightweight-kubernetes-distribution-first-experience/</link>
      <pubDate>Wed, 06 Mar 2019 16:25:56 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/k3s-lightweight-kubernetes-distribution-first-experience/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;K3S&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2019/k3s-150x137.png&#34;&gt;&lt;/p&gt;
&lt;p&gt;Rancher introduced alsmost week ago k3s, a lightweight Kubernetes Distribution. In the YouTube video below you hear Shannon Williams and Darren Shepherd from Rancher talk about K3S, what it is, the usecases and demo of K3S.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://youtu.be/5-5t672vFi4&#34;&gt;https://youtu.be/5-5t672vFi4&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://github.com/rancher/k3s&#34;&gt;k3s&lt;/a&gt;is a fully compliant, production-grade Kubernetes distribution that maintains an absolutely tiny footprint. Weighing in at less than 40 MB, it only needs 512 MB of RAM to run. This means it’s perfect for all kinds of computing that requires a minimal about of memory and space.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
