--- title: "#k3s articles | Hashnode" description: "Explore 84 articles tagged #k3s on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/k3s" --- Tag # #k3s 84 posts · 9 followers [Sanskriti Harmukh](https://hashnode.com/@sharmukh) · [Sep 3](https://hashnode.com/posts/installing-k3s-with-nvidia-gpu-operator-on-ubuntu-22-04/6a99a3a299e13496c86b51a1) ### [Installing K3s with NVIDIA GPU Operator on Ubuntu 22.04](https://vultr.hashnode.dev/installing-k3s-with-nvidia-gpu-operator-on-ubuntu-22-04?utm_source=hashnode&utm_medium=feed) Install K3s on a GPU-enabled Ubuntu 22.04 server, set up Helm, and deploy the NVIDIA GPU Operator to manage GPU resources in the cluster. 4 min read · [vultr.hashnode.dev](https://vultr.hashnode.dev/installing-k3s-with-nvidia-gpu-operator-on-ubuntu-22-04?utm_source=hashnode&utm_medium=feed) [Lalit Bagga](https://hashnode.com/@lbagga) · [Aug 11](https://hashnode.com/posts/i-wanted-kubernetes-without-an-always-on-eks-bill/6a7bb646c417cfd2d2c1df1f) ### [I Wanted Kubernetes Without an Always On EKS Bill](https://blog.lalitbagga.com/i-wanted-kubernetes-without-an-always-on-eks-bill?utm_source=hashnode&utm_medium=feed) I wanted a Kubernetes lab that would still be there the next morning. A temporary cluster on my laptop would be useful for testing manifests, but it would disappear when I closed the lid. Amazon EKS w 8 min read · [blog.lalitbagga.com](https://blog.lalitbagga.com/i-wanted-kubernetes-without-an-always-on-eks-bill?utm_source=hashnode&utm_medium=feed) [Angel Chavez](https://hashnode.com/@ElPadre12) · [Jul 23](https://hashnode.com/posts/standing-up-production-part-one/6a61818dd41a2d27938bcfe3) ### [Standing Up My Production Environment, Part One: Bootstrapping](https://blog.it-anc.cloud/standing-up-production-part-one?utm_source=hashnode&utm_medium=feed) A Flux Hero Story 3 min read · [blog.it-anc.cloud](https://blog.it-anc.cloud/standing-up-production-part-one?utm_source=hashnode&utm_medium=feed) [Albert Deutou](https://hashnode.com/@adeutou) · [Jul 22](https://hashnode.com/posts/self-hosting-like-a-pro-part-2-docker-k3s-and-traefik-v3-with-automatic-https/6a602db8672cd4d5a87f9c3c) ### [Self-Hosting Like a Pro, Part 2: Docker, K3s and Traefik v3 with Automatic HTTPS](https://blog-adeutou.hashnode.dev/self-hosting-like-a-pro-part-2-docker-k3s-and-traefik-v3-with-automatic-https?utm_source=hashnode&utm_medium=feed) installation of: a container runtime, a lightweight Kubernetes distribution, a modern reverse proxy, and automatic TLS certificates. By the end of this article, deploying an app with HTTPS will take one YAML file and zero manual certificate handling. 9 min read · [blog-adeutou.hashnode.dev](https://blog-adeutou.hashnode.dev/self-hosting-like-a-pro-part-2-docker-k3s-and-traefik-v3-with-automatic-https?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/self-hosting-like-a-pro-part-2-docker-k3s-and-traefik-v3-with-automatic-https/6a602db8672cd4d5a87f9c3c) [Angel Chavez](https://hashnode.com/@ElPadre12) · [Jul 17](https://hashnode.com/posts/self-hosting-audiobookshelf/6a598a4002f8fbdbec3a4c7c) ### [Self-Hosting Audiobookshelf](https://blog.it-anc.cloud/self-hosting-audiobookshelf?utm_source=hashnode&utm_medium=feed) A GitOps Build in Three Stages w/FluxCD 7 min read · [blog.it-anc.cloud](https://blog.it-anc.cloud/self-hosting-audiobookshelf?utm_source=hashnode&utm_medium=feed) [sanjay yadav](https://hashnode.com/@devopsbysanjay) · [May 22](https://hashnode.com/posts/k3s-vs-kubernetes-k8s-performance-architecture-use-cases-and-when-to-choose-each/6a0fe349d8e265f60d8e545d) ### [K3s vs Kubernetes (K8s): Performance, Architecture, Use Cases and When to Choose Each](https://devopsbysanjay.hashnode.dev/k3s-vs-kubernetes-k8s-performance-architecture-use-cases-and-when-to-choose-each?utm_source=hashnode&utm_medium=feed) K3s vs Kubernetes (K8s) comparison with architecture, performance, and use cases. Find the right choice for DevOps, edge, and production. 4 min read · [devopsbysanjay.hashnode.dev](https://devopsbysanjay.hashnode.dev/k3s-vs-kubernetes-k8s-performance-architecture-use-cases-and-when-to-choose-each?utm_source=hashnode&utm_medium=feed) [FortheXP](https://hashnode.com/@forthexp) · [May 5](https://hashnode.com/posts/gitops-without-exposure-hosting-a-site-from-your-own-hardware/69f9726046610fd606605c12) ### [GitOps Without Exposure: Hosting a Site from Your Own Hardware](https://forthexp.hashnode.dev/gitops-without-exposure-hosting-a-site-from-your-own-hardware?utm_source=hashnode&utm_medium=feed) Run a production-grade CD pipeline from your home lab — no cloud required 6 min read · [forthexp.hashnode.dev](https://forthexp.hashnode.dev/gitops-without-exposure-hosting-a-site-from-your-own-hardware?utm_source=hashnode&utm_medium=feed) [Jim Chundevalel](https://hashnode.com/@jchundevalel) · [Apr 26](https://hashnode.com/posts/k3scluster-part-5/69ee63a33d6a492cdd3e6560) ### [Part 5 - Nebula Sync: Keeping Two Pi-holes in Sync](https://accidentalcomplexity.hashnode.dev/k3scluster-part-5?utm_source=hashnode&utm_medium=feed) Some days the Pi-holes agree. Other days one of them develops opinions, and suddenly “redundancy” becomes a custody battle for DNS settings. 5 min read · [accidentalcomplexity.hashnode.dev](https://accidentalcomplexity.hashnode.dev/k3scluster-part-5?utm_source=hashnode&utm_medium=feed) [Jim Chundevalel](https://hashnode.com/@jchundevalel) · [Apr 25](https://hashnode.com/posts/k3scluster-part-2/69ebd973b463d4844c506a1f) ### [Part 2 - Network Design, Two Networks, and the IoT Problem](https://accidentalcomplexity.hashnode.dev/k3scluster-part-2?utm_source=hashnode&utm_medium=feed) When your IoT devices ask for network access, you give them a subnet, a firewall, a DNS policy, and the kind of trust normally reserved for raccoons near open trash cans. 6 min read · [accidentalcomplexity.hashnode.dev](https://accidentalcomplexity.hashnode.dev/k3scluster-part-2?utm_source=hashnode&utm_medium=feed) [Jim Chundevalel](https://hashnode.com/@jchundevalel) · [Apr 25](https://hashnode.com/posts/k3scluster-part-1/69ec0d06b463d4844c6c0e6b) ### [Part 1 - The Problem, The Plan, and The Foundation](https://accidentalcomplexity.hashnode.dev/k3scluster-part-1?utm_source=hashnode&utm_medium=feed) When you need a safe, you build an impregnable fortress. Then you add a moat. Then redundant DNS. Then Kubernetes. Then you start calling it “infrastructure.” 17 min read · [accidentalcomplexity.hashnode.dev](https://accidentalcomplexity.hashnode.dev/k3scluster-part-1?utm_source=hashnode&utm_medium=feed)