<?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>K3s on Wolkwacht</title>
    <link>https://wolkwacht.nl/tags/k3s/</link>
    <description>Recent content in K3s 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>Thu, 17 Oct 2019 10:37:20 +0000</lastBuildDate>
    <atom:link href="https://wolkwacht.nl/tags/k3s/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>k3s: Enable Traefik dashboard</title>
      <link>https://wolkwacht.nl/posts/k3s-enable-traefik-dashboard/</link>
      <pubDate>Thu, 17 Oct 2019 10:37:20 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/k3s-enable-traefik-dashboard/</guid>
      <description>&lt;p&gt;If you install k3s with the default settings it also installs Traefik as a load balancer. Traefik also offers a dashboard which is very easy to enable. If you go on your k3s machines to the path /var/lib/rancher/k3s/server/manifests you can find their traefik.yaml. To enable the Traefik dashboard you have to add &lt;em&gt;dashboard.enabled: &amp;ldquo;true&amp;rdquo;&lt;/em&gt; to the yaml.&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;root@k3s-master-1:/var/lib/rancher/k3s/server/manifests# cat traefik.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: traefik
  namespace: kube-system
spec:
  chart: https://%{KUBERNETES_API}%/static/charts/traefik-1.77.1.tgz
  set:
    rbac.enabled: &amp;#34;true&amp;#34;
    ssl.enabled: &amp;#34;true&amp;#34;
    metrics.prometheus.enabled: &amp;#34;true&amp;#34;
    kubernetes.ingressEndpoint.useDefaultPublishedService: &amp;#34;true&amp;#34;
    dashboard.enabled: &amp;#34;true&amp;#34;
root@k3s-master-1:/var/lib/rancher/k3s/server/manifests# cat traefik.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: traefik
  namespace: kube-system
spec:
  chart: https://%{KUBERNETES_API}%/static/charts/traefik-1.77.1.tgz
  set:
    rbac.enabled: &amp;#34;true&amp;#34;
    ssl.enabled: &amp;#34;true&amp;#34;
    metrics.prometheus.enabled: &amp;#34;true&amp;#34;
    kubernetes.ingressEndpoint.useDefaultPublishedService: &amp;#34;true&amp;#34;
    dashboard.enabled: &amp;#34;true&amp;#34;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;After a few minutes you will see some extra pods getting started.&lt;/p&gt;</description>
    </item>
    <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: release v0.2.0 released</title>
      <link>https://wolkwacht.nl/posts/k3s-release-v0-2-0-released/</link>
      <pubDate>Sat, 09 Mar 2019 07:34:42 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/k3s-release-v0-2-0-released/</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 has released v0.2.0.of k3s. Information of the new release is in this article. As soon as I have some time and I have added two extra nodes to the cluster, I&amp;rsquo;m going to add the cluster to my Rancher server. I have upgraded my Raspberry Pi&amp;rsquo;s to v0.2.0. The process of upgrading is really simple. Just download the new version and replace the old version of k3s with the new version and restart.&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>
