{"id":1869,"date":"2026-09-05T09:35:45","date_gmt":"2026-09-05T04:05:45","guid":{"rendered":"https:\/\/cpanelfree.com\/blog\/how-to-setup-lightweight-kubernetes-k3s-ubuntu-vps\/"},"modified":"2026-09-05T12:58:27","modified_gmt":"2026-09-05T07:28:27","slug":"how-to-setup-lightweight-kubernetes-k3s-ubuntu-vps","status":"publish","type":"post","link":"https:\/\/cpanelfree.com\/blog\/how-to-setup-lightweight-kubernetes-k3s-ubuntu-vps\/","title":{"rendered":"How to Set Up Lightweight Kubernetes (K3s) on a Budget Linux Cloud VPS"},"content":{"rendered":"

Demystifying Kubernetes: Why Standard K8s Fails on Budget VPS<\/h2>\n

Full enterprise Kubernetes distributions (such as kubeadm, OpenShift, or EKS) are designed for massive multi-node corporate data centers. Running standard Kubernetes requires separate control plane nodes, dedicated etcd clusters, extensive overlay networking daemons, and at least 4GB to 8GB of idle RAM just to bootstrap the control plane before launching a single application pod.<\/p>\n

K3s<\/strong> is a fully compliant, certified CNCF lightweight Kubernetes distribution created by Rancher Labs (SUSE). By packaging the control plane, Kubelet, Flannel CNI, CoreDNS, local path storage provisioners, and Traefik ingress controller into a single lightweight 100MB binary<\/strong>, K3s reduces memory consumption to under 512MB RAM. This enables developers and DevOps engineers to run production Kubernetes clusters, GitOps pipelines, and microservices on an affordable $4\u2013$10\/month cloud VPS.<\/p>\n

In this comprehensive hands-on tutorial, we will install K3s on Ubuntu 24.04\/22.04 LTS, configure kubectl<\/code> management on local workstations, deploy containerized microservice deployments with PersistentVolumeClaims, and configure automated Traefik ingress routing with SSL.<\/p>\n

Step 1: Installing K3s Control Plane on Ubuntu VPS<\/h2>\n

Installing K3s requires only a single official curl execution script that configures systemd daemons and network bridges automatically:<\/p>\n

# Update package list and install curl\nsudo apt update && sudo apt install -y curl\n\n# Install K3s control plane with Traefik enabled\ncurl -sfL https:\/\/get.k3s.io | sh -\n\n# Verify K3s systemd service status\nsudo systemctl status k3s --no-pager\n\n# Confirm node readiness via kubectl\nsudo k3s kubectl get nodes<\/code><\/pre>\n
Step 2: Configuring kubectl Access for Unprivileged Users & Remote Laptops<\/h2>\n
By default, K3s stores its kubeconfig at \/etc\/rancher\/k3s\/k3s.yaml<\/code> with restricted root permissions. Grant access to your standard user account:<\/p>\n
# Create local kube configuration directory\nmkdir -p ~\/.kube\nsudo cp \/etc\/rancher\/k3s\/k3s.yaml ~\/.kube\/config\nsudo chown $(id -u):$(id -g) ~\/.kube\/config\nchmod 600 ~\/.kube\/config\n\n# Verify kubectl command works without sudo\nkubectl get pods -A<\/code><\/pre>\n
To manage your K3s cluster from your local desktop laptop, copy ~\/.kube\/config<\/code> to your computer and replace 127.0.0.1<\/code> with your VPS server’s public IPv4 address.<\/p>\n
Step 3: Deploying a Scalable Web Application with Deployment & Service<\/h2>\n
Create a production deployment manifest webapp.yaml<\/code> running 3 replicated Nginx web app pods with an internal ClusterIP service:<\/p>\n
apiVersion: apps\/v1\nkind: Deployment\nmetadata:\n  name: web-app-deployment\n  labels:\n    app: web-app\nspec:\n  replicas: 3\n  selector:\n    matchLabels:\n      app: web-app\n  template:\n    metadata:\n      labels:\n        app: web-app\n    spec:\n      containers:\n      - name: nginx-web\n        image: nginx:alpine\n        ports:\n        - containerPort: 80\n        resources:\n          limits:\n            memory: \"64Mi\"\n            cpu: \"250m\"\n---\napiVersion: v1\nkind: Service\nmetadata:\n  name: web-app-service\nspec:\n  selector:\n    app: web-app\n  ports:\n  - protocol: TCP\n    port: 80\n    targetPort: 80<\/code><\/pre>\n
Apply the manifest to the cluster:<\/p>\n
kubectl apply -f webapp.yaml\nkubectl get pods -l app=web-app<\/code><\/pre>\n
Step 4: Exposing Microservices via Traefik Ingress Controller<\/h2>\n
K3s includes the Traefik Ingress controller out of the box. Create ingress.yaml<\/code> to route public HTTP traffic from your domain to the internal service:<\/p>\n
apiVersion: networking.k8s.io\/v1\nkind: Ingress\nmetadata:\n  name: web-app-ingress\n  annotations:\n    ingress.class: traefik\nspec:\n  rules:\n  - host: k8s.example.com\n    http:\n      paths:\n      - path: \/\n        pathType: Prefix\n        backend:\n          service:\n            name: web-app-service\n            port:\n              number: 80<\/code><\/pre>\n
Deploy the ingress router:<\/p>\n
kubectl apply -f ingress.yaml<\/code><\/pre>\n
Step 5: Installing Helm 3 Package Manager for Kubernetes<\/h2>\n
Helm simplifies deploying complex enterprise applications (such as Redis, PostgreSQL, WordPress, or Prometheus) using pre-packaged charts:<\/p>\n
# Download and install Helm 3 binary\ncurl https:\/\/raw.githubusercontent.com\/helm\/helm\/main\/scripts\/get-helm-3 | bash\n\n# Add Bitnami official chart repository\nhelm repo add bitnami https:\/\/charts.bitnami.com\/bitnami\nhelm repo update\n\n# Install a production-ready Redis cluster via Helm in 10 seconds\nhelm install my-redis bitnami\/redis --set auth.password=\"StrongRedisPass2026!\"<\/code><\/pre>\n
Standard Kubernetes (K8s) vs Lightweight K3s Benchmark<\/h2>\n\n\n\n\n\n\n\n
Feature \/ Metric<\/th>\nLightweight K3s (Rancher)<\/th>\nStandard Kubernetes (K8s \/ EKS)<\/th>\n<\/tr>\n<\/thead>\n
Idle RAM Consumption<\/strong><\/td>\n~350 MB to 512 MB<\/strong><\/td>\n~3.5 GB to 6.0 GB<\/td>\n<\/tr>\n
Installation Complexity<\/strong><\/td>\n1 Single Command (30 seconds)<\/strong><\/td>\nMulti-step manual node bootstrapping<\/td>\n<\/tr>\n
Included Ingress & Storage<\/strong><\/td>\nPre-packaged Traefik & Local Path<\/strong><\/td>\nRequires separate manual installs<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Deploying Persistent Volume Storage with Local-Path Provisioner<\/h2>\n
K3s includes Rancher’s lightweight local-path<\/code> storage class by default, allowing containerized stateful workloads (such as MySQL, PostgreSQL, or Redis) to dynamically request persistent host disk storage without requiring complex external SAN\/NFS arrays:<\/p>\n
apiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: database-pvc\nspec:\n  accessModes:\n    - ReadWriteOnce\n  storageClassName: local-path\n  resources:\n    requests:\n      storage: 10Gi<\/code><\/pre>\n
Automating Application Scaling with Horizontal Pod Autoscaler (HPA)<\/h2>\n
K3s includes the lightweight metrics-server out of the box. Automatically scale pod replicas up to 10 when CPU utilization exceeds 75%:<\/p>\n
# Enable Horizontal Pod Autoscaling on web-app-deployment\nkubectl autoscale deployment web-app-deployment --cpu-percent=75 --min=2 --max=10\n\n# Inspect active autoscaler metrics\nkubectl get hpa<\/code><\/pre>\n
Essential K3s Operational Commands Cheat Sheet<\/h2>\n