<?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 Haseeb Majid</title>
    <link>https://haseebmajid.dev/tags/k3s/</link>
    <description>Recent content in K3s on Haseeb Majid</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 02 Jun 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://haseebmajid.dev/tags/k3s/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TIL: How to Fix DNS Resolution Issues in K3s Related to Flannel Networking</title>
      <link>https://haseebmajid.dev/posts/2024-06-02-til-how-to-fix-dns-resolution-issues-in-k3s-related-to-flannel-networking/</link>
      <pubDate>Sun, 02 Jun 2024 00:00:00 +0000</pubDate>
      <author>Me</author>
      <guid>https://haseebmajid.dev/posts/2024-06-02-til-how-to-fix-dns-resolution-issues-in-k3s-related-to-flannel-networking/</guid>
      <description>&lt;p&gt;&lt;strong&gt;TIL: How to Fix DNS Resolution Issues in K3s Related to Flannel Networking&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Recently, I was trying to set up the kubernetes-dashboard, to make it easier to monitor my k8s cluster. I however noticed
I was getting the following error:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;… &amp;gt; add-kubernetes-dashboard via 🐹 v1.22.2 via   via ❄  impure &lt;span class=&#34;o&#34;&gt;(&lt;/span&gt;nix-shell-env&lt;span class=&#34;o&#34;&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt; k$ kubectl logs -n monitoring kubernetes-dashboard-kong-75bb76dd5f-b27ll
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;2024/05/05 20:55:21 &lt;span class=&#34;o&#34;&gt;[&lt;/span&gt;error&lt;span class=&#34;o&#34;&gt;]&lt;/span&gt; 1319#0: *274054 &lt;span class=&#34;o&#34;&gt;[&lt;/span&gt;lua&lt;span class=&#34;o&#34;&gt;]&lt;/span&gt; init.lua:371: execute&lt;span class=&#34;o&#34;&gt;()&lt;/span&gt;: DNS resolution failed: failed to receive reply from UDP server 10.43.0.10:53: timeout. Tried: nil, client: 127.0.0.1, server: kong, request: &lt;span class=&#34;s2&#34;&gt;&amp;#34;GET / HTTP/2.0&amp;#34;&lt;/span&gt;, host: &lt;span class=&#34;s2&#34;&gt;&amp;#34;localhost:8443&amp;#34;&lt;/span&gt;, request_id: &lt;span class=&#34;s2&#34;&gt;&amp;#34;af30b3162db70e2de8f1073a40f7d865&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Weird the DNS resolution seems to be failing, so I decided to follow the
&lt;a href=&#34;https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/&#34;&gt;Kubernetes guide&lt;/a&gt; to try to debug issues.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p><strong>TIL: How to Fix DNS Resolution Issues in K3s Related to Flannel Networking</strong></p>
<p>Recently, I was trying to set up the kubernetes-dashboard, to make it easier to monitor my k8s cluster. I however noticed
I was getting the following error:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">… &gt; add-kubernetes-dashboard via 🐹 v1.22.2 via   via ❄  impure <span class="o">(</span>nix-shell-env<span class="o">)</span>
</span></span><span class="line"><span class="cl"> k$ kubectl logs -n monitoring kubernetes-dashboard-kong-75bb76dd5f-b27ll
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl">2024/05/05 20:55:21 <span class="o">[</span>error<span class="o">]</span> 1319#0: *274054 <span class="o">[</span>lua<span class="o">]</span> init.lua:371: execute<span class="o">()</span>: DNS resolution failed: failed to receive reply from UDP server 10.43.0.10:53: timeout. Tried: nil, client: 127.0.0.1, server: kong, request: <span class="s2">&#34;GET / HTTP/2.0&#34;</span>, host: <span class="s2">&#34;localhost:8443&#34;</span>, request_id: <span class="s2">&#34;af30b3162db70e2de8f1073a40f7d865&#34;</span>
</span></span></code></pre></div><p>Weird the DNS resolution seems to be failing, so I decided to follow the
<a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/">Kubernetes guide</a> to try to debug issues.</p>
<p>I found out I couldn&rsquo;t even do a nslookup:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">kubectl <span class="nb">exec</span> -i -t dnsutils -- nslookup kubernetes.default
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="p">;;</span> connection timed out<span class="p">;</span> no servers could be reached
</span></span><span class="line"><span class="cl"><span class="nb">command</span> terminated with <span class="nb">exit</span> code <span class="m">1</span>
</span></span></code></pre></div><p>I had set up k3s on NixOS (as per the previous posts in this series). In the ended, the issue ending up being not
open the correct ports, we are using the <code>Flannel VXLAN</code> <sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup>. <code>UDP	8472	All nodes	All nodes	Required only for Flannel VXLAN</code>
The <a href="https://github.com/NixOS/nixpkgs/issues/175513#issuecomment-1147755254">GitHub</a> issue that helped me solve my problem.</p>
<p>We need to open up port 8472 in our firewall rules, on my NixOS server we can do something like so.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-nix" data-lang="nix"><span class="line"><span class="cl"><span class="p">{</span>
</span></span><span class="line"><span class="cl"><span class="n">networking</span><span class="o">.</span><span class="n">firewall</span> <span class="o">=</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">  <span class="n">allowedUDPPorts</span> <span class="o">=</span> <span class="p">[</span>
</span></span><span class="line"><span class="cl">    <span class="c1"># ...</span>
</span></span><span class="line"><span class="cl">    <span class="mi">8472</span>
</span></span><span class="line"><span class="cl">  <span class="p">];</span>
</span></span><span class="line"><span class="cl"><span class="p">}</span>
</span></span></code></pre></div><details
  class="notice danger"
  open="true"
>
    <summary class="notice-title">Security Issues</summary>
  
  The VXLAN port on nodes should not be exposed to the world as it opens up your cluster network to be accessed by anyone. Run your nodes behind a firewall/security group that disables access to port 8472.
</details>

<p>So in my case, since my k8s cluster was multi-node, the nodes couldn&rsquo;t communicate with each other properly.
That&rsquo;s about it, it took me a while to figure out, basically RTFM 😭😭😭.</p>
<div class="footnotes" role="doc-endnotes">
<hr>
<ol>
<li id="fn:1">
<p><a href="https://docs.k3s.io/installation/requirements#networking">https://docs.k3s.io/installation/requirements#networking</a>&#160;<a href="#fnref:1" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
</ol>
</div>
]]></content:encoded>
    </item>
    
    <item>
      <title>How to Deploy Kubernetes Dashboard Using Pulumi to a K3s Cluster</title>
      <link>https://haseebmajid.dev/posts/2024-05-24-how-to-deploy-kubernetes-dashboard-using-pulumi-to-a-k3s-cluster/</link>
      <pubDate>Fri, 24 May 2024 00:00:00 +0000</pubDate>
      <author>Me</author>
      <guid>https://haseebmajid.dev/posts/2024-05-24-how-to-deploy-kubernetes-dashboard-using-pulumi-to-a-k3s-cluster/</guid>
      <description>&lt;details
  class=&#34;notice warn&#34;
  open=&#34;true&#34;
&gt;
    &lt;summary class=&#34;notice-title&#34;&gt;Kubernetes Knowledge&lt;/summary&gt;
  
  I don&amp;rsquo;t know a ton about Kubernetes. I am still learning, hence this home-lab project. So there may be better ways
to do stuff that I have described below. If that is the case, please let me know! Just take what I say with a pinch of
salt.
&lt;/details&gt;

&lt;p&gt;It&amp;rsquo;s been a while since I made an update about my home lab, also an aside, I should&amp;rsquo;ve given this series a better name.
So recently, I finally went back to my PI cluster and started to actually setup properly. The first thing I decided
to put on it was the Kubernetes dashboard. I could get a nice GUI look into what is happening with my cluster at a
glance. It also looked simple to deploy.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<details
  class="notice warn"
  open="true"
>
    <summary class="notice-title">Kubernetes Knowledge</summary>
  
  I don&rsquo;t know a ton about Kubernetes. I am still learning, hence this home-lab project. So there may be better ways
to do stuff that I have described below. If that is the case, please let me know! Just take what I say with a pinch of
salt.
</details>

<p>It&rsquo;s been a while since I made an update about my home lab, also an aside, I should&rsquo;ve given this series a better name.
So recently, I finally went back to my PI cluster and started to actually setup properly. The first thing I decided
to put on it was the Kubernetes dashboard. I could get a nice GUI look into what is happening with my cluster at a
glance. It also looked simple to deploy.</p>
<p>I want to have all my k8s config in code, so I decided to deploy it with helm and Pulumi. One of the nice things about
Pulumi is I can configure resources in a programming language I know, i.e. Go vs having to use Terraform. Which I am
sort of familiar with but no expert.</p>
<p>So, if you have followed my previous posts, we have a working PI k3s cluster running on NixOS. We have also enabled Tailscale
to make it easier to connect to. Now to actually put &ldquo;things&rdquo; on our cluster.</p>
<h2 id="getting-started">Getting Started</h2>
<p>If you are using Nix we can use a flake devshell like so to install Pulumi and some other useful tools. In <code>flake.nix</code></p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-nix" data-lang="nix"><span class="line"><span class="cl"><span class="p">{</span>
</span></span><span class="line"><span class="cl">  <span class="n">description</span> <span class="o">=</span> <span class="s2">&#34;Developer Shell&#34;</span><span class="p">;</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl">  <span class="n">inputs</span> <span class="o">=</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">    <span class="n">nixpkgs</span><span class="o">.</span><span class="n">url</span> <span class="o">=</span> <span class="s2">&#34;github:nixos/nixpkgs/nixos-unstable&#34;</span><span class="p">;</span>
</span></span><span class="line"><span class="cl">  <span class="p">};</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl">  <span class="n">outputs</span> <span class="o">=</span> <span class="p">{</span><span class="n">nixpkgs</span><span class="o">,</span> <span class="o">...</span><span class="p">}:</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">    <span class="n">devShell</span><span class="o">.</span><span class="n">x86_64-linux</span> <span class="o">=</span> <span class="k">let</span>
</span></span><span class="line"><span class="cl">      <span class="n">pkgs</span> <span class="o">=</span> <span class="n">nixpkgs</span><span class="o">.</span><span class="n">legacyPackages</span><span class="o">.</span><span class="n">x86_64-linux</span><span class="p">;</span>
</span></span><span class="line"><span class="cl">    <span class="k">in</span>
</span></span><span class="line"><span class="cl">      <span class="n">pkgs</span><span class="o">.</span><span class="n">mkShell</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">        <span class="n">packages</span> <span class="o">=</span> <span class="k">with</span> <span class="n">pkgs</span><span class="p">;</span> <span class="p">[</span>
</span></span><span class="line"><span class="cl">          <span class="n">sops</span>
</span></span><span class="line"><span class="cl">          <span class="n">go</span>
</span></span><span class="line hl"><span class="cl">          <span class="n">pulumi</span>
</span></span><span class="line"><span class="cl">          <span class="n">pulumiPackages</span><span class="o">.</span><span class="n">pulumi-language-go</span>
</span></span><span class="line"><span class="cl">          <span class="n">kubernetes-helm</span>
</span></span><span class="line"><span class="cl">          <span class="n">k9s</span>
</span></span><span class="line"><span class="cl">          <span class="n">kubectl</span>
</span></span><span class="line"><span class="cl">        <span class="p">];</span>
</span></span><span class="line"><span class="cl">      <span class="p">};</span>
</span></span><span class="line"><span class="cl">  <span class="p">};</span>
</span></span><span class="line"><span class="cl"><span class="p">}</span>
</span></span></code></pre></div><p>Combined with direnv (<code>.envrc</code>), we can load into this shell automatically when we change directories to this folder.
So we don&rsquo;t need to have these packages installed globally, we can have them just setup when we need them for this project.</p>
<p>However, it doesn&rsquo;t really matter whether you use Nix or not. You just need to work out how to install Pulumi on your machine.
One thing to remember is this is on our development machine, which will connect to our cluster and deploy our config.
We don&rsquo;t need these tools installed on our PI cluster.</p>
<h2 id="pulumi">Pulumi</h2>
<p>We can either use Pulumi locally, i.e. store state locally. Or use their managed service, to make my life easier
I created a Pulumi account. Just note, you don&rsquo;t need to use their propriety managed platform if you don&rsquo;t want to.
It just the easiest way to get started and not have to worry about sharing state between machines.
This includes state so that Pulumi knows what is installed on the k3s cluster.</p>
<h3 id="managed-platform">Managed Platform</h3>
<p>So first create an account or login to Pulumi. Then we need to create a new project on Pulumi I am going to create a
new Kubernetes project like so:</p>
<p><img
        loading="lazy"
        src="/posts/2024-05-24-how-to-deploy-kubernetes-dashboard-using-pulumi-to-a-k3s-cluster/images/pulumi-project.png"
        type=""
        alt="Pulumi Project"
        
      />
<img
        loading="lazy"
        src="/posts/2024-05-24-how-to-deploy-kubernetes-dashboard-using-pulumi-to-a-k3s-cluster/images/pulumi-kubernetes.png"
        type=""
        alt="Pulumi Kubernetes Template"
        
      /></p>
<p>We now have a new project and stack. I still fully understand the difference, but it seems we can have multiple stacks
per project. So perhaps this could be useful if we had different environments, such as dev/prod. But we want to keep
them in the same project.</p>
<p>In our case, we will keep it simple with a project called <code>home-lab</code> and stack called <code>main</code> (I am bad at naming things).
Then go to your home-lab project folder, the one above with the <code>flake.nix</code> at the root. Then run
<code>pulumi new kubernetes-go -s hmajid2301/home-lab/main</code>. Replace the 2nd part with your own username/project/stack.
This will now give us some boilerplate and set up a <code>go.mod</code>, <code>go.sum</code> and <code>main.go</code> file we can use.</p>
<h3 id="test-deploy">Test Deploy</h3>
<details
  class="notice info"
  open="true"
>
    <summary class="notice-title">KUBECONFIG</summary>
  
  Pulumi will the default KUBECONFIG found typically at <code>~/.kube/config</code>. In my case, I use <code>~/.kube/config.personal</code>
so I set the <code>KUBECONFIG</code> environment variable inside my <code>flake.nix</code> to point to this config file.
</details>

<p>We can then do deploy what is in our <code>main.go</code> with <code>pulumi up</code>, which will deploy a new nginx app.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go"><span class="line"><span class="cl"><span class="kn">package</span><span class="w"> </span><span class="nx">main</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kn">import</span><span class="w"> </span><span class="p">(</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="nx">appsv1</span><span class="w"> </span><span class="s">&#34;github.com/pulumi/pulumi-kubernetes/sdk/v4/go/kubernetes/apps/v1&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="nx">corev1</span><span class="w"> </span><span class="s">&#34;github.com/pulumi/pulumi-kubernetes/sdk/v4/go/kubernetes/core/v1&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="nx">metav1</span><span class="w"> </span><span class="s">&#34;github.com/pulumi/pulumi-kubernetes/sdk/v4/go/kubernetes/meta/v1&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="s">&#34;github.com/pulumi/pulumi/sdk/v3/go/pulumi&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kd">func</span><span class="w"> </span><span class="nf">main</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">Run</span><span class="p">(</span><span class="kd">func</span><span class="p">(</span><span class="nx">ctx</span><span class="w"> </span><span class="o">*</span><span class="nx">pulumi</span><span class="p">.</span><span class="nx">Context</span><span class="p">)</span><span class="w"> </span><span class="kt">error</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">appLabels</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nx">StringMap</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="s">&#34;app&#34;</span><span class="p">:</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">&#34;nginx&#34;</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="p">}</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">deployment</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">appsv1</span><span class="p">.</span><span class="nf">NewDeployment</span><span class="p">(</span><span class="nx">ctx</span><span class="p">,</span><span class="w"> </span><span class="s">&#34;app-dep&#34;</span><span class="p">,</span><span class="w"> </span><span class="o">&amp;</span><span class="nx">appsv1</span><span class="p">.</span><span class="nx">DeploymentArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="nx">Spec</span><span class="p">:</span><span class="w"> </span><span class="nx">appsv1</span><span class="p">.</span><span class="nx">DeploymentSpecArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">				</span><span class="nx">Selector</span><span class="p">:</span><span class="w"> </span><span class="o">&amp;</span><span class="nx">metav1</span><span class="p">.</span><span class="nx">LabelSelectorArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">					</span><span class="nx">MatchLabels</span><span class="p">:</span><span class="w"> </span><span class="nx">appLabels</span><span class="p">,</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">				</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">				</span><span class="nx">Replicas</span><span class="p">:</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">Int</span><span class="p">(</span><span class="mi">1</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">				</span><span class="nx">Template</span><span class="p">:</span><span class="w"> </span><span class="o">&amp;</span><span class="nx">corev1</span><span class="p">.</span><span class="nx">PodTemplateSpecArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">					</span><span class="nx">Metadata</span><span class="p">:</span><span class="w"> </span><span class="o">&amp;</span><span class="nx">metav1</span><span class="p">.</span><span class="nx">ObjectMetaArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">						</span><span class="nx">Labels</span><span class="p">:</span><span class="w"> </span><span class="nx">appLabels</span><span class="p">,</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">					</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">					</span><span class="nx">Spec</span><span class="p">:</span><span class="w"> </span><span class="o">&amp;</span><span class="nx">corev1</span><span class="p">.</span><span class="nx">PodSpecArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">						</span><span class="nx">Containers</span><span class="p">:</span><span class="w"> </span><span class="nx">corev1</span><span class="p">.</span><span class="nx">ContainerArray</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">							</span><span class="nx">corev1</span><span class="p">.</span><span class="nx">ContainerArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">								</span><span class="nx">Name</span><span class="p">:</span><span class="w">  </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">&#34;nginx&#34;</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">								</span><span class="nx">Image</span><span class="p">:</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">&#34;nginx&#34;</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">							</span><span class="p">}},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">					</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">				</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="p">})</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="p">}</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">ctx</span><span class="p">.</span><span class="nf">Export</span><span class="p">(</span><span class="s">&#34;name&#34;</span><span class="p">,</span><span class="w"> </span><span class="nx">deployment</span><span class="p">.</span><span class="nx">Metadata</span><span class="p">.</span><span class="nf">Name</span><span class="p">())</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="kc">nil</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="p">})</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><h3 id="dashboard">Dashboard</h3>
<p>However, we want to deploy the Kubernetes dashboard. So let&rsquo;s do the following, create a new file called <code>dashboard.go</code>.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go"><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kd">func</span><span class="w"> </span><span class="nf">addDashboard</span><span class="p">(</span><span class="nx">ctx</span><span class="w"> </span><span class="o">*</span><span class="nx">pulumi</span><span class="p">.</span><span class="nx">Context</span><span class="p">)</span><span class="w"> </span><span class="kt">error</span><span class="w"> </span><span class="p">{}</span><span class="w">
</span></span></span></code></pre></div><p>We will call this function from our <code>main.go</code> like:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go"><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kn">package</span><span class="w"> </span><span class="nx">main</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kn">import</span><span class="w"> </span><span class="p">(</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="s">&#34;github.com/pulumi/pulumi/sdk/v3/go/pulumi&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kd">func</span><span class="w"> </span><span class="nf">main</span><span class="p">()</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">Run</span><span class="p">(</span><span class="kd">func</span><span class="p">(</span><span class="nx">ctx</span><span class="w"> </span><span class="o">*</span><span class="nx">pulumi</span><span class="p">.</span><span class="nx">Context</span><span class="p">)</span><span class="w"> </span><span class="kt">error</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nf">addDashboard</span><span class="p">(</span><span class="nx">ctx</span><span class="p">)</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="p">}</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="kc">nil</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="p">})</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>Now when we run <code>pulumi up</code>, it will look at our <code>main.go</code> and then call the <code>addDashboard</code> function.
Now let&rsquo;s create all the specific resources we need for the dashboard.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go"><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kd">func</span><span class="w"> </span><span class="nf">addDashboard</span><span class="p">(</span><span class="nx">ctx</span><span class="w"> </span><span class="o">*</span><span class="nx">pulumi</span><span class="p">.</span><span class="nx">Context</span><span class="p">)</span><span class="w"> </span><span class="kt">error</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="nx">namespace</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="s">&#34;monitoring&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="nx">_</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="nx">helmv3</span><span class="p">.</span><span class="nf">NewChart</span><span class="p">(</span><span class="nx">ctx</span><span class="p">,</span><span class="w"> </span><span class="s">&#34;kubernetes-dashboard&#34;</span><span class="p">,</span><span class="w"> </span><span class="nx">helmv3</span><span class="p">.</span><span class="nx">ChartArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">Chart</span><span class="p">:</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">&#34;kubernetes-dashboard&#34;</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">FetchArgs</span><span class="p">:</span><span class="w"> </span><span class="nx">helmv3</span><span class="p">.</span><span class="nx">FetchArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="nx">Repo</span><span class="p">:</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">`https://kubernetes.github.io/dashboard/`</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">Namespace</span><span class="p">:</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="nx">namespace</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="p">})</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="p">}</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// ...</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>First let&rsquo;s define a namespace variable, this is the namespace in Kubernetes that the dashboard will be deployed to.
I am going to create a new namespace <code>monitoring</code>. Then we install a new helm chart, which provide an easy way to install
applications into Kubernetes.  Whilst also providing us with some options to tweak the application to our liking.</p>
<p>Normally, we could lock our dependencies using a <code>chart.lock</code> file; however, it seems Pulumi does not respect this at
the moment <sup id="fnref:1"><a href="#fn:1" class="footnote-ref" role="doc-noteref">1</a></sup>. This is enough to get the dashboard working. We could do a <code>pulumi up</code>.</p>
<p>Then after the deployment check the pods using <code>kubectl get pods -n monitoring</code>.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">&gt; kubectl get pods -n monitoring
</span></span><span class="line"><span class="cl">NAME                                                    READY   STATUS    RESTARTS       AGE
</span></span><span class="line"><span class="cl">kubernetes-dashboard-metrics-scraper-7f6f977dc9-n7mhn   1/1     Running   <span class="m">1</span> <span class="o">(</span>122m ago<span class="o">)</span>   38h
</span></span><span class="line"><span class="cl">kubernetes-dashboard-web-f5d66867c-sk9ms                1/1     Running   <span class="m">1</span> <span class="o">(</span>122m ago<span class="o">)</span>   38h
</span></span><span class="line"><span class="cl">kubernetes-dashboard-auth-9688d4ccf-ntdm6               1/1     Running   <span class="m">1</span> <span class="o">(</span>122m ago<span class="o">)</span>   38h
</span></span><span class="line"><span class="cl">kubernetes-dashboard-kong-75bb76dd5f-k29x7              1/1     Running   <span class="m">1</span> <span class="o">(</span>122m ago<span class="o">)</span>   38h
</span></span><span class="line"><span class="cl">kubernetes-dashboard-api-7dc9dc68df-xrfs7               1/1     Running   <span class="m">2</span> <span class="o">(</span>119m ago<span class="o">)</span>   38h
</span></span></code></pre></div><p>However, to have permissions to login into the dashboard via the web GUI we need to create some more resources.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-go" data-lang="go"><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="kd">func</span><span class="w"> </span><span class="nf">addDashboard</span><span class="p">(</span><span class="nx">ctx</span><span class="w"> </span><span class="o">*</span><span class="nx">pulumi</span><span class="p">.</span><span class="nx">Context</span><span class="p">)</span><span class="w"> </span><span class="kt">error</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="nx">namespace</span><span class="w"> </span><span class="o">:=</span><span class="w"> </span><span class="s">&#34;monitoring&#34;</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="c1">// ...</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="nx">_</span><span class="p">,</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="p">=</span><span class="w"> </span><span class="nx">rbacv1</span><span class="p">.</span><span class="nf">NewClusterRoleBinding</span><span class="p">(</span><span class="nx">ctx</span><span class="p">,</span><span class="w"> </span><span class="s">&#34;cluster-admin-binding&#34;</span><span class="p">,</span><span class="w"> </span><span class="o">&amp;</span><span class="nx">rbacv1</span><span class="p">.</span><span class="nx">ClusterRoleBindingArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">Metadata</span><span class="p">:</span><span class="w"> </span><span class="nx">metav1</span><span class="p">.</span><span class="nx">ObjectMetaArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="nx">Name</span><span class="p">:</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">&#34;admin-user&#34;</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">RoleRef</span><span class="p">:</span><span class="w"> </span><span class="nx">rbacv1</span><span class="p">.</span><span class="nx">RoleRefArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="nx">Name</span><span class="p">:</span><span class="w">     </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">&#34;cluster-admin&#34;</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="nx">ApiGroup</span><span class="p">:</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">&#34;rbac.authorization.k8s.io&#34;</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="nx">Kind</span><span class="p">:</span><span class="w">     </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">&#34;ClusterRole&#34;</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="nx">Subjects</span><span class="p">:</span><span class="w"> </span><span class="nx">rbacv1</span><span class="p">.</span><span class="nx">SubjectArray</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="nx">rbacv1</span><span class="p">.</span><span class="nx">SubjectArgs</span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">				</span><span class="nx">Kind</span><span class="p">:</span><span class="w">      </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="s">&#34;ServiceAccount&#34;</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">				</span><span class="nx">Name</span><span class="p">:</span><span class="w">      </span><span class="nx">svc</span><span class="p">.</span><span class="nx">Metadata</span><span class="p">.</span><span class="nf">Name</span><span class="p">().</span><span class="nf">Elem</span><span class="p">(),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">				</span><span class="nx">Namespace</span><span class="p">:</span><span class="w"> </span><span class="nx">pulumi</span><span class="p">.</span><span class="nf">String</span><span class="p">(</span><span class="nx">namespace</span><span class="p">),</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">			</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="p">},</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="p">})</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="k">if</span><span class="w"> </span><span class="nx">err</span><span class="w"> </span><span class="o">!=</span><span class="w"> </span><span class="kc">nil</span><span class="w"> </span><span class="p">{</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">		</span><span class="k">return</span><span class="w"> </span><span class="nx">err</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">	</span><span class="p">}</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">    </span><span class="k">return</span><span class="w"> </span><span class="kc">nil</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="p">}</span><span class="w">
</span></span></span></code></pre></div><p>What we are doing here is creating a role binding, for a new admin-user, which has full privilege to modify the cluster.
Likely later we will want to change this to a read-only user. As we are only accessing the dashboard with this user.</p>
<p>You can see the equivalent YAML we are applying here <sup id="fnref:2"><a href="#fn:2" class="footnote-ref" role="doc-noteref">2</a></sup>:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">ServiceAccount</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">admin-user</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">namespace</span><span class="p">:</span><span class="w"> </span><span class="l">kubernetes-dashboard</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nn">---</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l">rbac.authorization.k8s.io/v1</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">ClusterRoleBinding</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">metadata</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">admin-user</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">roleRef</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">apiGroup</span><span class="p">:</span><span class="w"> </span><span class="l">rbac.authorization.k8s.io</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">ClusterRole</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">cluster-admin</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="nt">subjects</span><span class="p">:</span><span class="w">
</span></span></span><span class="line"><span class="cl">- <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l">ServiceAccount</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">admin-user</span><span class="w">
</span></span></span><span class="line"><span class="cl"><span class="w">  </span><span class="nt">namespace</span><span class="p">:</span><span class="w"> </span><span class="l">kubernetes-dashboard</span><span class="w">
</span></span></span></code></pre></div><p>Then run <code>pulumi up</code>, to create these resources again.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl"><span class="c1"># Copy JWT to clipboard that we use to login</span>
</span></span><span class="line"><span class="cl">kubectl -n monitoring create token admin-user <span class="p">|</span> wl-copy
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl"><span class="c1"># Setup port forwarding so we can access the proxy pod locally on httsp://localhost:8443</span>
</span></span><span class="line"><span class="cl">kubectl -n monitoring port-forward services/kubernetes-dashboard-kong-proxy 8443:443
</span></span></code></pre></div><p>After that, we can get a secret token, we will need to log in to the dashboard. Then we port forward to the proxy pod,
so we can now access the dashboard at <code>https://localhost:8443</code>. Ignore the SSL/TLS warnings, as the certificates are
self-signed. I will likely do a post about how we can fix this later, once I have figured it out myself.</p>
<p><img
        loading="lazy"
        src="/posts/2024-05-24-how-to-deploy-kubernetes-dashboard-using-pulumi-to-a-k3s-cluster/images/login.png"
        type=""
        alt="Login"
        
      />
<img
        loading="lazy"
        src="/posts/2024-05-24-how-to-deploy-kubernetes-dashboard-using-pulumi-to-a-k3s-cluster/images/dashboard.png"
        type=""
        alt="Dashboard"
        
      /></p>
<p>That&rsquo;s it! We&rsquo;ve deployed something to our Kubernetes cluster, woo-hoo!!!!</p>
<div class="footnotes" role="doc-endnotes">
<hr>
<ol>
<li id="fn:1">
<p><a href="https://github.com/pulumi/pulumi-kubernetes/issues/2669">https://github.com/pulumi/pulumi-kubernetes/issues/2669</a>&#160;<a href="#fnref:1" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
<li id="fn:2">
<p><a href="https://upcloud.com/resources/tutorials/deploy-kubernetes-dashboard">https://upcloud.com/resources/tutorials/deploy-kubernetes-dashboard</a>&#160;<a href="#fnref:2" class="footnote-backref" role="doc-backlink">&#x21a9;&#xfe0e;</a></p>
</li>
</ol>
</div>
]]></content:encoded>
    </item>
    
    <item>
      <title>TIL: How to Use Tailscale to Connect to K3S PI Cluster</title>
      <link>https://haseebmajid.dev/posts/2023-12-20-til-how-to-use-tailscale-to-connect-to-k3s-pi-cluster/</link>
      <pubDate>Wed, 20 Dec 2023 00:00:00 +0000</pubDate>
      <author>Me</author>
      <guid>https://haseebmajid.dev/posts/2023-12-20-til-how-to-use-tailscale-to-connect-to-k3s-pi-cluster/</guid>
      <description>&lt;p&gt;&lt;strong&gt;TIL: How to Use Tailscale to Connect to K3S PI Cluster&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;So what do we do if want to connect to our K3S cluster running our RPIs, but we are not on the same network/at home.
Well we can look to use a VPN, in this article we will be using &lt;a href=&#34;https://tailscale.com/&#34;&gt;tailscale&lt;/a&gt;. It is super easy
to setup on NixOS, and we need very little config for Tailscale. It also has a generous free tier, which will be
more than enough for our home lab use case.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p><strong>TIL: How to Use Tailscale to Connect to K3S PI Cluster</strong></p>
<p>So what do we do if want to connect to our K3S cluster running our RPIs, but we are not on the same network/at home.
Well we can look to use a VPN, in this article we will be using <a href="https://tailscale.com/">tailscale</a>. It is super easy
to setup on NixOS, and we need very little config for Tailscale. It also has a generous free tier, which will be
more than enough for our home lab use case.</p>
<p>So essentially, what we will need to do is have a Tailscale service always running on each of PI hosts, though we
could have it running on our main control node only (called strawberry from me, see previous articles in this series
for more context). Once we start the service we will need to auth with Tailscale the first time, manually though.</p>
<p>The device we want to connect to our cluster from will also need to be running the Tailscale VPN, but we only need it
running when we want to access our cluster.</p>
<p>All we need to do is add a line to our <code>common.nix</code>, this line <code>services.tailscale.enable = true;</code>. We can then
deploy this using Colmena like <code>colmena apply switch --build-on-target</code>. This will deploy tailscale onto each our PI
cluster nodes.</p>
<p>Then to authenticate with Tailscale we can ssh to our node and run the following <code>sudo tailscale up</code>. We can then auth
in the browser by logging in. We can then also see the device on the Tailscale website.</p>
<p><img
        loading="lazy"
        src="/posts/2023-12-20-til-how-to-use-tailscale-to-connect-to-k3s-pi-cluster/images/tailscale.png"
        type=""
        alt="Tailscale GUI"
        
      /></p>
<p>Then where before I might use <code>strawberry.local</code> to connect now I can use <code>strawberry</code> when I am on the Tailscale VPN.
Note if you want self host rather than using Tailscale, there is an open source project called
<a href="https://github.com/juanfont/headscale">headscale</a>.</p>
<p>That&rsquo;s it! We deployed Tailscale and can connect to our PI K3S cluster, from anywhere.</p>
]]></content:encoded>
    </item>
    
    <item>
      <title>How to Deploy K3s With Colmena on Pi Cluster</title>
      <link>https://haseebmajid.dev/posts/2023-12-16-how-to-deploy-k3s-with-colmena-on-pi-cluster/</link>
      <pubDate>Sat, 16 Dec 2023 00:00:00 +0000</pubDate>
      <author>Me</author>
      <guid>https://haseebmajid.dev/posts/2023-12-16-how-to-deploy-k3s-with-colmena-on-pi-cluster/</guid>
      <description>&lt;p&gt;In this post, we will go over how we can deploy K3S on our PI cluster we have set up. Which is running NixOS,
and we can also pass secrets using sops nix based on the previous parts of this series.&lt;/p&gt;
&lt;p&gt;Some of you maybe wondering what is &lt;a href=&#34;https://k3s.io/&#34;&gt;K3S&lt;/a&gt;, it is a Kubernetes distribution which is tiny i.e.
the binary is only 50 MB. It also has fewer dependencies. Make it perfect our PI cluster and home lab and IoT apps.
I am still going to work out how to manage the Kubernetes cluster itself, perhaps I will use Pulumi you could also
terraform if you wanted a reproducible PI cluster.&lt;/p&gt;</description>
      <content:encoded><![CDATA[<p>In this post, we will go over how we can deploy K3S on our PI cluster we have set up. Which is running NixOS,
and we can also pass secrets using sops nix based on the previous parts of this series.</p>
<p>Some of you maybe wondering what is <a href="https://k3s.io/">K3S</a>, it is a Kubernetes distribution which is tiny i.e.
the binary is only 50 MB. It also has fewer dependencies. Make it perfect our PI cluster and home lab and IoT apps.
I am still going to work out how to manage the Kubernetes cluster itself, perhaps I will use Pulumi you could also
terraform if you wanted a reproducible PI cluster.</p>
<p>In our <code>common.nix</code>, let&rsquo;s enable the k3s service which will start k3s for us, one of the nice things about Nix. We
will also add the token that the K3S nodes will need to communicate with each other:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-nix" data-lang="nix"><span class="line"><span class="cl"><span class="p">{</span>
</span></span><span class="line"><span class="cl">  <span class="n">services</span><span class="o">.</span><span class="n">k3s</span><span class="o">.</span><span class="n">enable</span> <span class="o">=</span> <span class="no">true</span><span class="p">;</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl">  <span class="n">sops</span><span class="o">.</span><span class="n">secrets</span><span class="o">.</span><span class="n">k3s_token</span> <span class="o">=</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">    <span class="n">sopsFile</span> <span class="o">=</span> <span class="sr">./secrets.yaml</span><span class="p">;</span>
</span></span><span class="line"><span class="cl">  <span class="p">};</span>
</span></span><span class="line"><span class="cl">
</span></span><span class="line"><span class="cl">  <span class="n">services</span><span class="o">.</span><span class="n">k3s</span><span class="o">.</span><span class="n">tokenFile</span> <span class="o">=</span> <span class="n">config</span><span class="o">.</span><span class="n">sops</span><span class="o">.</span><span class="n">secrets</span><span class="o">.</span><span class="n">k3s_token</span><span class="o">.</span><span class="n">path</span><span class="p">;</span>
</span></span><span class="line"><span class="cl"><span class="p">}</span>
</span></span></code></pre></div><p>This needs to be secret, so we will use the sops-nix. In my case, I deployed the main node and then took the key
from the node itself and shared it with the agents, so they can join the cluster. However, when we start the main node
we can also pass it a token we specify. Sops saves the token to a file; hence we use <code>tokenFile</code> here, as we cannot
actually access the value in our nix config.</p>
<p>We may also want to update our firewall, and open ports so that the nodes in the cluster can communicate each other
from the hosts.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-nix" data-lang="nix"><span class="line"><span class="cl"><span class="p">{</span>
</span></span><span class="line"><span class="cl">  <span class="n">networking</span><span class="o">.</span><span class="n">firewall</span> <span class="o">=</span> <span class="p">{</span>
</span></span><span class="line"><span class="cl">    <span class="n">allowedTCPPorts</span> <span class="o">=</span> <span class="p">[</span>
</span></span><span class="line"><span class="cl">      <span class="mi">22</span>
</span></span><span class="line"><span class="cl">      <span class="mi">6443</span>
</span></span><span class="line"><span class="cl">      <span class="mi">6444</span>
</span></span><span class="line"><span class="cl">      <span class="mi">9000</span>
</span></span><span class="line"><span class="cl">    <span class="p">];</span>
</span></span><span class="line"><span class="cl">    <span class="n">enable</span> <span class="o">=</span> <span class="no">true</span><span class="p">;</span>
</span></span><span class="line"><span class="cl">  <span class="p">};</span>
</span></span><span class="line"><span class="cl"><span class="p">}</span>
</span></span></code></pre></div><p>We don&rsquo;t need to do much else for the main node, but for each agent node we need to tell it is that it should act
as an agent, and which hostname to connect to join the nodes. Which we can do something like this <code>mango.nix</code>;</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-nix" data-lang="nix"><span class="line"><span class="cl"><span class="p">{</span>
</span></span><span class="line"><span class="cl">  <span class="n">services</span><span class="o">.</span><span class="n">k3s</span><span class="o">.</span><span class="n">role</span> <span class="o">=</span> <span class="s2">&#34;agent&#34;</span><span class="p">;</span>
</span></span><span class="line"><span class="cl">  <span class="n">services</span><span class="o">.</span><span class="n">k3s</span><span class="o">.</span><span class="n">serverAddr</span> <span class="o">=</span> <span class="s2">&#34;https://strawberry.local:6443&#34;</span><span class="p">;</span>
</span></span><span class="line"><span class="cl"><span class="p">}</span>
</span></span></code></pre></div><p>Where they are all running in the same local network; hence they can connect using the hostname and <code>.local</code>. This was
avahi service we set up in a previous post.</p>
<p>So in each 3 of my agent nodes this config is copies, so these nodes act as agents and connect to the k8s cluster
correctly. We can then deploy the app as we normally would using Colmena, <code>colmena apply switch --build-on-target</code>.</p>
<p>Then we can follow this <a href="https://docs.k3s.io/cluster-access">tutorial</a> for cluster access using <code>kubectl</code>. We can
then check all the nodes in the cluster by doing:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"><span class="line"><span class="cl">kubectl get nodes
</span></span><span class="line"><span class="cl">NAME         STATUS   ROLES                  AGE   VERSION
</span></span><span class="line"><span class="cl">strawberry   Ready    control-plane,master   41d   v1.27.6+k3s1
</span></span><span class="line"><span class="cl">orange       Ready    &lt;none&gt;                 34d   v1.27.6+k3s1
</span></span><span class="line"><span class="cl">mango        Ready    &lt;none&gt;                 32d   v1.27.6+k3s1
</span></span><span class="line"><span class="cl">guava        Ready    &lt;none&gt;                 35d   v1.27.6+k3s1
</span></span></code></pre></div><p>That&rsquo;s it! We successfully deployed k3s to our PI cluster using Colmena and even sops-nix from our previous posts.
In the next post, we will look at how we can add Tailscale to be able to securely connect to our cluster from anywhere.</p>
]]></content:encoded>
    </item>
    
  </channel>
</rss>
