<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kevin Goos on Medium]]></title>
        <description><![CDATA[Stories by Kevin Goos on Medium]]></description>
        <link>https://medium.com/@kevingoos?source=rss-53a1a7723533------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Sm-1N2aTQK_TzcyA6OIssA.jpeg</url>
            <title>Stories by Kevin Goos on Medium</title>
            <link>https://medium.com/@kevingoos?source=rss-53a1a7723533------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:17:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kevingoos/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[K3S: Setup MetalLB using BGP on Pfsense]]></title>
            <link>https://kevingoos.medium.com/k3s-setup-metallb-using-bgp-on-pfsense-f5ff1165f6d4?source=rss-53a1a7723533------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5ff1165f6d4</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[pfsense]]></category>
            <category><![CDATA[bgp]]></category>
            <dc:creator><![CDATA[Kevin Goos]]></dc:creator>
            <pubDate>Sat, 09 Jul 2022 15:03:14 GMT</pubDate>
            <atom:updated>2022-07-12T20:48:53.224Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6K_m2G58AvhKrJfeFbkVEw.png" /><figcaption>Setup picture</figcaption></figure><p>For my internal K3S cluster I need a loadbalancer. While I can easily setup an nginx loadbalancer in front, I prefer to make the loadbalancer part of the cluster. So that it is also redundant.</p><p>For that cause MetalLB is a good fit. MetalLB has 2 different modes: Layer2 and BGP.</p><h3>Layer2 mode</h3><p>While layer2 mode will work fine, communicating over ARP. There are two disadvantages why I didn’t chose this option. First in layer2 mode there is a single elected leader. This means in turn that all traffic is send over this 1 single node. Second sometimes clients will handle the ARP cache incorrectly and this can cause a slow failover.</p><h3>BGP mode</h3><p>While BPG is harder to setup, because the router need to get the updates from the cluster. This will not have the above limitations. The only limitation there is, is when a node goes down, all active connections are broken. So this means users that have an active connection will get the “Connection reset by peer” message. But the failover will be instant.</p><h3>Prepare PFSense</h3><p>Install FRR package, goto System =&gt; Package Manager =&gt; Available Packages. And install the FRR package.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OMPLpdem3oT6KZ-OPuP7Mg.png" /></figure><p>Now we go to the FFR settings under Services =&gt; FFR Global/Zebra.</p><p>First we have to setup the global settings. This means setting checking Enable FRR, setup Default Router ID (you’re default router IP) and Master Password (Random generated)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pJx_Tk325yWNADDUA9Y_VQ.png" /><figcaption>FRR global settings</figcaption></figure><p>Next we go to the BGP settings. You can find it in the tabs on top or you can go there by going to Services =&gt; FRR BGP</p><p>So here we have to again Enable BGP Routing, and set the Router Id again. Because I am working inside a subnet I also define the Network to Distribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z4Cfo1gJ9rwMn5MOVTZ5gw.png" /><figcaption>BGP settings Part 1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dEs5jbkkCxAq4gWGs2rGew.png" /><figcaption>BGP settings Part 2</figcaption></figure><p>Next we have to define our neighbors. This you can find in the Neighbors tab of course. We define 2 neighbors here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fH8Hwkn26DLQFt1wFFJC6A.png" /><figcaption>Neighbors defined</figcaption></figure><p>First we start with defining the Peer Group. We give it a name and set the Remote AS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t4OVKnhTd0J40eZeHCR7eg.png" /><figcaption>Peer group definition</figcaption></figure><p>Next we define our Master node where metallb is running on so it can send BGP commands to our router.</p><p>We define the Address from the master node, you then give it a description and add it in the correct Peer Group. Last we also define the Remote AS again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O2ZzyV6AzyHda-OJ2oU3jA.png" /></figure><p>After this setup pfsense is ready to receive BGP Commands from metalLB</p><h3>Configuring MetalLB</h3><pre>apt install curl sudo gnupg</pre><h3>Configuring MetalLB</h3><p>First we create a config map used for configuring the metallb-pod.</p><p>So we create a file called metallb-values.yaml</p><pre>apiVersion: v1<br>kind: ConfigMap<br>metadata:<br>  namespace: metallb-system<br>  name: metallb<br>data:<br>  config: |<br>    peers:<br>    - peer-address: 10.10.0.1<br>      peer-asn: 64512<br>      my-asn: 64513<br>    address-pools:<br>    - name: default<br>      protocol: bgp<br>      addresses:<br>      - 10.10.10.100-10.10.10.255</pre><p>Then we install metallb using helm, and apply the config.</p><pre>helm repo add metallb <a href="https://metallb.github.io/metallb">https://metallb.github.io/metallb</a><br>helm repo update</pre><pre>kubectl create namespace metallb-system<br>helm install -n metallb-system metallb metallb/metallb -f metallb-values.yaml<br>kubectl create configmap metallb --from-file=metallb-values.yaml</pre><p>If there are changes in the furture to the config, they can easily be applied using the following command:</p><pre>kubectl apply -f metallb-values.yaml</pre><h3>Testing Metallb loadbalancer</h3><p>Now we will test if the above config is working:</p><pre>kubectl create deploy nginx --image nginx<br>kubectl expose deploy nginx --port 80 --type LoadBalancer</pre><p>Now we need to figure out if the loadbalancer receives an IP.</p><pre>kubectl get services</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*uyiE_4nTL6v6x3pUoYgBrg.png" /><figcaption>External IP gets appointed</figcaption></figure><p>You can also find the registered ip in PFSense under the status tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/477/1*rEDaBxfj4O9ZapSV7SZwpg.png" /><figcaption>PFSense output</figcaption></figure><p>As you can see, the nginx loadbalancer service gets an external ip given by the router.</p><pre>kubectl delete service nginx</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5ff1165f6d4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing K3S in an LXC container]]></title>
            <link>https://kevingoos.medium.com/installing-k3s-in-an-lxc-container-2fc24b655b93?source=rss-53a1a7723533------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fc24b655b93</guid>
            <category><![CDATA[proxmox]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[lxc]]></category>
            <dc:creator><![CDATA[Kevin Goos]]></dc:creator>
            <pubDate>Fri, 01 Jul 2022 14:33:11 GMT</pubDate>
            <atom:updated>2022-07-12T20:18:22.707Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n_RU3r7lgjMhWCye3mvWZA.png" /><figcaption>Proxmox + LXC + Kubernetes</figcaption></figure><p>In the previous part I informed everybody on how I setup an LXC container in Proxmox ready to install Docker and Kubernetes. Now in this tutorial I will take you through the installation of Docker and after that K3S which is a lightweight kubernetes cluster.</p><h3>Why K3S over K8S</h3><p>K3S is a lightweight kubernetes version which is created by rancher. Here we get all the basic components we need, and K3S can almost run on any device. So the perfect choise for my cluster.</p><h3>Setup K3S</h3><p>So now that we have an LXC container we can start with the installation. But the same installation will apply to a VM is you choise to go that way. After all the preperations we did in part 1, it is just one simple command:</p><pre>curl -sfL <a href="https://get.k3s.io/">https://get.k3s.io</a> | sh -s - server --disable servicelb --disable traefik --write-kubeconfig-mode 644</pre><h3>Setup default config for server</h3><p>Now the cluster is running, but we need to export the config so that the kubectl running on the server, knows where it need to go:</p><pre>export KUBECONFIG=/etc/rancher/k3s/k3s.yaml</pre><p>After this command we can start executing kubectl commands. To test is we execute the following command, and hopefully we get the response expected:</p><pre>kubectl get nodes</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m9eCGLdEp5sM0baAQGxaRA.png" /><figcaption>Output</figcaption></figure><h3>Setup kubectl on local windows shell</h3><p>We don’t want to connect to the shell from the server all the time. So we setup the local shell to run kubectl commands on the server through the kubernetes API.</p><p>To install kubectl on you’re local computer, I used chocolaty package manager to install it. But there are also standalone binary’s. I will not explain how to install it, but point you to the documentation to find you’re way off working: <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/">https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/</a></p><p>So we have to get the current config from the server, and apply it to you’re personal computer. The following command will show the config if you run it on you’re server:</p><pre>cat /etc/rancher/k3s/k3s.yaml</pre><p>This command will output a config that you then can copy to you’re local computer:</p><pre>apiVersion: v1<br>clusters:<br>- cluster:<br> certificate-authority-data: [some-key]<br> server: <a href="https://127.0.0.1:6443/">https://127.0.0.1:6443</a><br> name: default<br>contexts:<br>- context:<br> cluster: default<br> user: default<br> name: default<br>current-context: default<br>kind: Config<br>preferences: {}<br>users:<br>- name: default<br> user:<br> client-certificate-data: [some-other-key]</pre><p>So we need to create a file called <strong>config</strong> inside the following location: C:\users\[user]\.kube</p><p>If the folder .kube doesn’t exist yet, you can just create it yourself.</p><p>Importanted to change the server address from <a href="https://127.0.0.1:6443/">https://127.0.0.1:6443</a> to the correct IP address from the server where it need to connect to. (Example: <a href="https://127.0.0.1:6443/">https://192.168.1.50:6443</a>)</p><h3>Install helm (on local machine)</h3><p>Helm is an easy CLI used to install and deploy kubernetes pods. We will install this here, but use it in the next parts of the tutorial to install prepared packages, easier.</p><pre>curl https://baltocdn.com/helm/signing.asc | sudo apt-key add -<br>sudo apt-get install apt-transport-https --yes<br>echo &quot;deb https://baltocdn.com/helm/stable/debian/ all main&quot; | sudo tee /etc/apt/sources.list.d/helm-stable-debian.list<br>sudo apt-get update<br>sudo apt-get install helm</pre><h3>Finally</h3><p>Now we have a working basic cluster where we can deploy pods. But the next problem will be, how we give access to pods from the outside. So in the next part we will start setting up a loadbalancer so that we can get adresses assigned to the pods.</p><h3>Next chapter:</h3><p><a href="https://kevingoos.medium.com/installing-k3s-in-an-lxc-container-2fc24b655b93">https://kevingoos.medium.com/installing-k3s-in-an-lxc-container-2fc24b655b93</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fc24b655b93" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Minecraft server on debian, the full explanation…]]></title>
            <link>https://kevingoos.medium.com/minecraft-server-on-debian-the-full-explanation-32e3676e0393?source=rss-53a1a7723533------2</link>
            <guid isPermaLink="false">https://medium.com/p/32e3676e0393</guid>
            <category><![CDATA[minecraft-server-host]]></category>
            <category><![CDATA[minecraft]]></category>
            <category><![CDATA[dns]]></category>
            <dc:creator><![CDATA[Kevin Goos]]></dc:creator>
            <pubDate>Sun, 19 Dec 2021 17:07:13 GMT</pubDate>
            <atom:updated>2021-12-19T17:07:13.501Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Header image" src="https://cdn-images-1.medium.com/max/1024/1*uXBjIPJyYAMf-lJHz5qYFw.png" /></figure><p>After a question from my friend, I decided to setup a Minecraft server. But what look to be an easy task, took me almost 2 days to do. The problem being, that documentation is scattered all over the internet. So my intent with this article is to gather all the information I found, and guide you to a decent setup Minecraft instance.</p><h3>1. Instal debian</h3><p>While installation of a new Linux instance is easy for me. It mostly depends on the underlying system that is being used. I use Proxmox as virtualisation environment so I just created an LXC container running Debian buster.</p><p>Some default applications I install (but you can use whatever you prefer):</p><pre>apt install vim, sudo -y</pre><h3>2. Minecraft server itself</h3><p>For this step, my friend prepared the full setup of the Minecraft server itself (using Fabric).</p><p>The first question you need to ask yourself is what version of Minecraft do you want to use, 1.18.1, … And after that, will it be vanilla? Or do we want to use a modloader like Fabric, Forge, … I think there is enough documentation easily accessible depending on which version you want to use.</p><h3>3. Setup users</h3><p>Both for the FTP and the service later in the article we need a user, so first we setup the user profiles.</p><p>This can be simple done with the following command:</p><pre>adduser username</pre><p>And for the service user we add some extra parameters (-s /sbin/nologin will block the user from logging in, and -r will make it a system user, -U will create a group with the same name as the user):</p><pre>useradd -r -s /sbin/nologin -U minecraft</pre><p>So lastly we want to also add the other user to the new group:</p><pre>usermod -a -G minecraft username</pre><h3>3. Uploading files to the server (optional)</h3><p>SCP for uploading the files to the server would work perfect, but because my friend is not really a command line guru we picked the option of using an FTP client/server setup. For the client you can pick whatever software you want, but for the server we used VSFTP.</p><p>First I started by creating the folder where the server while exists.</p><pre>mkdir /opt/minecraft</pre><p>Then, installation is done by the following command.</p><pre>apt-get install vsftpd -y</pre><p>And the last step is setting up the configuration file. The best is first to backup the default file, so that you can look back in the future.</p><pre>mv /etc/vsftpd.conf /etc/vsftpd.conf.bk<br>vim /etc/vsftpd.conf</pre><p>This is the config file I ended up with:</p><pre>listen=YES<br>listen_ipv6=NO<br>anonymous_enable=NO<br>local_enable=YES<br>write_enable=YES<br>dirmessage_enable=YES<br>use_localtime=YES</pre><pre>allow_writeable_chroot=YES<br>pam_service_name=vsftpd</pre><pre>user_sub_token=$USER<br>local_root=/opt/minecraft</pre><pre>userlist_enable=YES<br>userlist_file=/etc/vsftpd.userlist<br>userlist_deny=NO</pre><pre>local_umask=011</pre><p>We also setup the file configured in the above config file:</p><pre>vim /etc/vsftpd.userlist</pre><p>This will contain all the users that you want to give access to the FTP server.</p><p>After that a quick restart of the service will get everything up in running order:</p><pre>sudo service vsftpd restart</pre><h3>4. Testing the server</h3><p>After you upload you can try starting the server, normally everything should run.</p><p>First switch to the minecraft user:</p><pre>java -jar fabric-server.jar</pre><p>Depending how you named you’re jarfile this will change a bit. And also you can setup the right amounts of memory you want to use.</p><pre>java -Xms4G -Xmx8G -jar fabric-server.jar</pre><p>And if the server startup correctly you can also connect to it in you’re local network.</p><h3>4. Port forward (if friends want access over the internet)</h3><p>So for giving other people access to you’re server you need to open a port on you’re router, the default port is 25565 for minecraft (unless you changed the port inside server.properties file). Forwarding this on you’re router or ISP modem depends on which device you have. So a quick search on google will solve this for you.</p><h3>5. Service? (optional but preferred)</h3><p>In debian you can create a service to keep the server running, after a crash or even after reboot. For this we need to add another config file.</p><pre>vim /etc/systemd/system/minecraft.service</pre><p>And the config file contains the following configuration:</p><pre>[Unit]<br>Description=Teamsepak Minecraft Server<br>After=network.target</pre><pre>[Service]<br>ExecStart=java -Xms4G -Xmx15G -jar fabric-server.jar</pre><pre>User=minecraft<br>Group=minecraft</pre><pre>WorkingDirectory=/opt/minecraft/fabric-multidc-1.18.1/</pre><pre>TimeoutStartSec=0<br>Restart=always<br>RestartSec=30</pre><pre>[Install]<br>WantedBy=default.target</pre><p>After saving this config file, we need to reload and start the service:</p><pre>systemctl daemon-reload<br>systemctl start minecraft.service</pre><p>Now it should be up in running and to check this you can use the following command:</p><pre>systemctl status minecraft.service</pre><p>The ouput should like this, showing the active (running):</p><figure><img alt="Status of the service" src="https://cdn-images-1.medium.com/max/846/1*oJUpbkFBW44505U276Zm6w.png" /></figure><p>Also if you want to follow the service logs you can use the following command to output all the log lines to the console.</p><pre>journalctl -f</pre><h3>5a. DNS for first Minecraft server (optional)</h3><p>The last step is giving you’re friends easier access. Always typing in the ip of you’re ISP is annoying so that is why there exists domain names. For a small 6 euro / month you get access to a domain name (and there are also free options). I use OVH as my domain vendor, so all the setup steps will be from the OVH domain manager UI.</p><p>So pointing you’re domain name to you’re ISP is easy, just create an A record with the IP.</p><figure><img alt="Setup A record" src="https://cdn-images-1.medium.com/max/614/1*vCkXyzpiyUyMvh5urIxeqg.png" /></figure><h3>5b. DNS, you’re second Minecraft server (optional)</h3><p>But what if this is you’re second or third server on a different port? Of course you can just add the port at the end of the URL (minecraft.mydomain.be:25566). But then you’re user need to remember which port the server was running on.</p><p>This is why Minecraft support SRV record, they will tell you’re Minecraft client on which port the user need to connect. The setup is also not that difficult, you just need to know what you need to input where.</p><p>First you create an A record again</p><figure><img alt="Create an A record" src="https://cdn-images-1.medium.com/max/615/1*r4ZsuIdwNlniZCc_Ww7CBg.png" /></figure><p>And now you create the SRV record:</p><figure><img alt="Create an SRV record" src="https://cdn-images-1.medium.com/max/611/1*OGJVyhVjD5AVkSw0gDdXIA.png" /></figure><p>Here you see:</p><ul><li>Sub-domain: <br>_minecraft._tcp.minecraft2.mydomain.be<br>- _minecraft = name of the service<br>- _tcp = protocol<br>- minecraft2 = same subdomain as the A record created</li><li>Priority: This decides which records comes first.</li><li>Weight: After priority we look at weight for who comes first.</li><li>Target: this is the same as the A record.</li></ul><h3>Disclaimer</h3><p>So after this you normally have a running server which people can easily access, from everywhere. I am also not an expert at these topics so there are probably things that can be optimised. And if there are you can always let me know and maybe I will adapt both my setup and this article. But this is what I currently figured out, and the most import thing is that it works for me for now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32e3676e0393" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes inside Proxmox LXC]]></title>
            <link>https://kevingoos.medium.com/kubernetes-inside-proxmox-lxc-cce5c9927942?source=rss-53a1a7723533------2</link>
            <guid isPermaLink="false">https://medium.com/p/cce5c9927942</guid>
            <category><![CDATA[lxc]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[proxmox]]></category>
            <dc:creator><![CDATA[Kevin Goos]]></dc:creator>
            <pubDate>Tue, 23 Feb 2021 15:02:48 GMT</pubDate>
            <atom:updated>2022-07-02T09:38:59.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x1s_NhCX8ixZgYIjUKW3Fw.png" /></figure><p>So you want to run Kubernetes on Proxmox, but you don’t want to use all the resources a VM is using. Then LXC containers is an option. But for setting up Kubernetes inside an LXC container you need to setup some special sauce.</p><h3>Step 1: prepare the host</h3><p>Because LXC containers share the host’s kernel, we have to prepare the host. This means disabling the swap and also loading a couple of modules.</p><p>First I adapt the sysctl file on the host:</p><pre>vim /etc/sysctl.conf</pre><p>Uncomment the following line:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*0obgiRRBZAMZzTZg5USHIw.png" /></figure><p>And add:</p><pre>vm.swapiness=0</pre><p><strong>Disable swap:</strong></p><pre>swapoff -a</pre><p>After that adapt the fstab file:</p><pre>vim /etc/fstab</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*uiaS-B3OYdTpq3ydCOrABQ.png" /><figcaption>Disable swap on host</figcaption></figure><p>I did a reboot of the full host, I don’t know if this is needed but wanted to be sure…</p><h3>Step 2: Create an LXC container</h3><p>I both tested with Ubuntu and Debian, but for Debian it is important that you’re Proxmox version is at least 7.0.0. Else you will get errors…</p><p><strong>Make the container unprivileged:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/1*h_D6X0c_vCZHoWn9szgBVA.png" /><figcaption>Setting up LXC to unprivileged</figcaption></figure><p><strong>Disable swap inside the container:<br></strong>Kubernetes will not initialize if the swap is not disabled.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*mP28FFxKLtkB99a2RP0Zvw.png" /><figcaption>Disable swap</figcaption></figure><p><strong>Enable nesting:<br></strong>You can find this options under “Options” after creating the LXC container.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/305/1*7kjlWFOHUeDdHuxdoWDEgA.png" /><figcaption>Features: nesting=1</figcaption></figure><h3>Step 3: Change container config file</h3><p>Before we startup the LXC container, we have to change the config file that is created.</p><p><strong>Edit the config file of the container:<br></strong>You can locate the config file here: <em>“/etc/pve/lxc/$ID.conf”. </em>The $ID need to be filled in with the container ID of the container you just created. You can find the ID in front of the name.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/146/1*9zG80Lv7ygwvjQb__Pl35Q.png" /><figcaption>Container ID</figcaption></figure><p><strong>Add the following to the config file:</strong></p><pre><em>lxc.apparmor.profile: unconfined<br>lxc.cgroup2.devices.allow: a<br>lxc.cap.drop:<br>lxc.mount.auto: &quot;proc:rw sys:rw&quot;</em></pre><h3>Step 4: Apply some configuration inside the LXC container</h3><p>For the last step we have to create some missing files inside of the container, because in the Proxmox Ubuntu LXC template they are missing.</p><p><strong>Create /etc/rc.local</strong></p><pre>#!/bin/sh -e<br># Kubeadm 1.15 needs /dev/kmsg to be there, but it’s not in lxc, but we can just use /dev/console instead<br># see: <a href="https://github.com/kubernetes-sigs/kind/issues/662">https://github.com/kubernetes-sigs/kind/issues/662</a></pre><pre>if [ ! -e /dev/kmsg ]; then<br>ln -s /dev/console /dev/kmsg<br>fi</pre><pre># <a href="https://medium.com/@kvaps/run-kubernetes-in-lxc-container-f04aa94b6c9c">https://medium.com/@kvaps/run-kubernetes-in-lxc-container-f04aa94b6c9c</a><br>mount --make-rshared /</pre><p>After creating this file we setup the permissions and reboot.</p><pre>chmod +x /etc/rc.local<br>/etc/rc.local</pre><h3>Finally</h3><p>Now the LXC container is setup for running Kubernetes. Also a handy tip, create a template so that you can spin up extra nodes very fast. The next steps are installing and setup of Kubernetes, which I will cover in part 2.</p><h3>Next chapter:</h3><p><a href="https://kevingoos.medium.com/installing-k3s-in-an-lxc-container-2fc24b655b93">https://kevingoos.medium.com/installing-k3s-in-an-lxc-container-2fc24b655b93</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cce5c9927942" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>