diff --git a/content/post/running-k3s-in-lxc-on-proxmox/index.md b/content/post/running-k3s-in-lxc-on-proxmox/index.md
index 298ad04b..bba432d6 100644
--- a/content/post/running-k3s-in-lxc-on-proxmox/index.md
+++ b/content/post/running-k3s-in-lxc-on-proxmox/index.md
@@ -1,5 +1,5 @@
---
-title: "Running k3s in LXC on Proxmox"
+title: "Running K3s in LXC on Proxmox"
date: 2021-11-14T10:07:03-05:00
lastmod: 2021-11-14T10:07:03-05:00
draft: false
@@ -9,14 +9,11 @@ tags: ["k3s", "proxmox", "lxc", "self-hosted"]
categories: []
author: ""
-# You can also close(false) or open(true) something for this content.
-# P.S. comment can only be closed
comment: false
toc: false
autoCollapseToc: false
postMetaInFooter: false
hiddenFromHomePage: false
-# You can also define another contentCopyright. e.g. contentCopyright: "This is another copyright."
contentCopyright: false
reward: false
mathjax: false
@@ -31,8 +28,6 @@ sequenceDiagrams:
options: ""
---
-
-
It has been a while since I've actively used Kubernetes and wanted to explore the evolution of tools such as [Helm](https://helm.sh) and [Tekton](https://tekton.dev). I decided to deploy [K3s](https://k3s.io), since I've had success with deploying it on resource-contrained Raspberry Pis in the past. I thought that this time it'd be convenient to have K3s running in a LXC container on Proxmox. This would allow for easy snapshotting of the entire Kubernetes deployment. LXC containers also provide an efficient way to use a machine's resources.
## What is K3s?
diff --git a/public/blog/2021/11/14/running-k3s-in-lxc-on-proxmox/index.html b/public/blog/2021/11/14/running-k3s-in-lxc-on-proxmox/index.html
index 4e1a27e5..d7109522 100644
--- a/public/blog/2021/11/14/running-k3s-in-lxc-on-proxmox/index.html
+++ b/public/blog/2021/11/14/running-k3s-in-lxc-on-proxmox/index.html
@@ -1,19 +1,19 @@
- Running k3s in LXC on Proxmox - davegallant
-
+ Running K3s in LXC on Proxmox - davegallant
+
-
-
+
+
-
-
+
+
@@ -102,7 +102,7 @@
-
Running k3s in LXC on Proxmox
+
Running K3s in LXC on Proxmox
Posted on Nov 14, 2021
@@ -187,7 +187,8 @@ As of 2021/11, it is still defaulting to the 1.19 channel, so I overrode it to 1
NAME REFERENCE TARGETS MINPODS MAXPODS REPLICAS AGE
horizontalpodautoscaler.autoscaling/tekton-pipelines-webhook Deployment/tekton-pipelines-webhook 9%/100% 1 5 1 12h
I made sure to install Tailscale in the container so that I can easily access K3s from anywhere.
-
If I’m feeling adventurous, I might experiment with K3s rootless.
+
If I’m feeling adventurous, I might experiment with K3s rootless.