Deploy and administer K3s clusters with embedded etcd and custom CNI.
npx skills add https://github.com/kettleofketchup/KettleOfSkills --skill k3s-kettleofketchup
Please help me install this Agent Skill. Skill: k3s Source: https://github.com/kettleofketchup/KettleOfSkills/tree/main/plugins/k3s/skills/k3s Command: npx skills add https://github.com/kettleofketchup/KettleOfSkills --skill k3s-kettleofketchup
Deploying and managing lightweight Kubernetes clusters for edge, IoT, homelab, or resource-constrained environments often requires specialized configuration for high availability, airgapped deployments, custom networking, and private registries, which can be complex and error-prone without targeted guidance.
Use the k3s skill to configure a 3-node high-availability K3s cluster with embedded etcd, Calico CNI, and private registry support for your homelab environment.
High-intent search queries and answers about installing and using this skill.
To install a high-availability K3s cluster, configure multiple server nodes using embedded etcd. This provides a resilient multi-node setup optimized for edge and homelab environments without requiring an external database.
Yes, you can replace the default Flannel CNI with Calico or Cilium in K3s. This allows you to implement custom networking requirements and advanced network policies within your lightweight Kubernetes distribution.
Deploying K3s in an airgapped environment involves using pre-packaged images and configuring private container registries. This ensures isolated installation and operation without requiring direct internet access to pull dependencies.
Yes, K3s integrates with NixOS modules to support infrastructure as code workflows. You can define and manage your lightweight Kubernetes cluster configuration declaratively alongside your system setup.
Troubleshooting K3s involves managing K3s component disabling and debugging containerd and kubelet runtime settings. This helps identify and resolve node-level failures and container lifecycle issues in your cluster.
Setting up a private registry is recommended for multi-node K3s homelab setups. It ensures consistent and reliable image pulling across server and agent nodes, especially when deploying custom self-hosted workloads.
yongseongkimDeploy the Sunrei application to a k3s cluster with OCI images and Helm charts.
EmeaAppGbbDeploy and manage containerized AI agents on Microsoft Foundry with azd.
kettleofketchupDeploy, configure, and troubleshoot Calico for Kubernetes cluster networking.
alicangnllDetect container escape vulnerabilities and privilege escalation paths in Docker and Kubernetes environments.
