deploy: ef5ff1bde8c9245ae6c471a0d3e8a46e3c67364d

This commit is contained in:
davegallant
2021-11-15 00:55:54 +00:00
parent 1bf162f4ad
commit fb4a150ec4
2 changed files with 3 additions and 3 deletions

View File

@@ -157,9 +157,9 @@ personal blog
</div>
</header>
<div class="container entry-content">
<p>It has been a while since I&rsquo;ve actively used Kubernetes and wanted to explore the evolution of tools like Helm and Tekton. I decided to deploy <a href=https://k3s.io>K3s</a>, since I&rsquo;ve had success with deploying it on resource-contrained Raspberry Pis in the past. I thought that this time it&rsquo;d be convenient to have K3s running in a LXC container on Proxmox. This would allow for backing up the LXC container with the entire Kubernetes deployment. LXC containers also enable an efficient way to squeeze as much out of the machine resources as possible.</p>
<p>It has been a while since I&rsquo;ve actively used Kubernetes and wanted to explore the evolution of tools like Helm and Tekton. I decided to deploy <a href=https://k3s.io>K3s</a>, since I&rsquo;ve had success with deploying it on resource-contrained Raspberry Pis in the past. I thought that this time it&rsquo;d be convenient to have K3s running in a LXC container on Proxmox. This would allow for backing up the LXC container with the entire Kubernetes deployment. LXC containers provide an efficient way to squeeze as much out of the machine resources as possible.</p>
<h2 id=what-is-k3s>What is K3s?</h2>
<p>K3s is a Kubernetes distro that advertises itself as a lightweight binary with a much smaller memory-footprint than traditional k8s. K3s is not a fork and seeks to remain as close to upstream as it can while maintaining a small set of patches.</p>
<p>K3s is a Kubernetes distro that advertises itself as a lightweight binary with a much smaller memory-footprint than traditional k8s. K3s is not a fork of k8s as it seeks to remain as close to upstream as it possibly can.</p>
<h2 id=configure-proxmox>Configure Proxmox</h2>
<p>This <a href=https://gist.github.com/triangletodd/02f595cd4c0dc9aac5f7763ca2264185>gist</a> contains snippets and discussion on how to deploy K3s in LXC on proxmox. It mentions that <code>bridge-nf-call-iptables</code> should be loaded, but I did not understand the benefit of doing this.</p>
<h2 id=disable-swap>Disable swap</h2>

File diff suppressed because one or more lines are too long