Managing the Deployment with Rancher

Rancher is a free, open-source web dashboard for running Kubernetes. Once your services run on a Kubernetes cluster, Rancher lets you see every workload, scale it, roll out a new image, roll back and read logs from a browser instead of typing kubectl commands. This guide installs Rancher on your own Linux server or VPS, imports an existing cluster such as k3s, and covers day-to-day management of a deployed service.

1. What Rancher does, and when you need it

Kubernetes runs your containers; Rancher is a management layer on top. It is most useful when:

• you look after more than one cluster, or want a team to manage deployments without handing out cluster-admin credentials;
• you want a visual view of workloads, pods, logs and events;
• you want role-based access, so a developer can redeploy one app but not touch the rest.

If you run one small k3s cluster alone, kubectl and Helm may be all you need. Rancher adds memory use and one more system to keep updated.

2. What you need

• A Linux server with root access, running a current distribution such as Ubuntu LTS, Debian, AlmaLinux or Rocky Linux. CentOS 7 and CentOS Linux 8 are end of life; don't build new servers on them.
• Enough memory. Rancher itself is memory-hungry. As a starting point, give the server running Rancher 8 GB of RAM or more, especially if your applications run on the same node. Check the current requirements in the Rancher documentation before you size production servers.
• A hostname, such as rancher.yourbusiness.in, with an A record pointing to the server's public IP address. Rancher uses this name for its certificate and for connecting clusters.
• kubectl and Helm on the server or on your computer.

3. Install Rancher on k3s with Helm (recommended)

This puts Rancher on a single-node k3s cluster. Rancher supports only certain Kubernetes versions, so check the Rancher support matrix first and install a matching k3s version.

Steps 3 and 4 as commands:

# cert-manager
helm repo add jetstack https://charts.jetstack.io
helm repo update
helm install cert-manager jetstack/cert-manager \
  --namespace cert-manager --create-namespace \
  --set crds.enabled=true

# Rancher
helm repo add rancher-stable https://releases.rancher.com/server-charts/stable
helm repo update
kubectl create namespace cattle-system
helm install rancher rancher-stable/rancher \
  --namespace cattle-system \
  --set hostname=rancher.yourbusiness.in \
  --set bootstrapPassword='choose-a-long-random-password' \
  --set ingress.tls.source=letsEncrypt \
  --set [email protected] \
  --set letsEncrypt.ingress.class=traefik

kubectl -n cattle-system rollout status deploy/rancher

k3s ships with the Traefik ingress controller, which is why the ingress class is traefik. Let's Encrypt can issue the certificate only if the hostname already resolves to the server and ports 80 and 443 are open.

On first login, Rancher asks for the bootstrap password, then makes you set a new admin password and confirm the server URL. If you didn't set a bootstrap password, read the generated one with:

kubectl get secret --namespace cattle-system bootstrap-secret \
  -o go-template='{{.data.bootstrapPassword|base64decode}}{{"\n"}}'

4. The quick Docker install (testing only)

For a throwaway lab, Rancher still runs as a single container on a server that has Docker:

docker run -d --restart=unless-stopped \
  -p 80:80 -p 443:443 --privileged \
  rancher/rancher:<version>
docker logs <container-id> 2>&1 | grep "Bootstrap Password:"

5. Import your application cluster

If your services run on a separate cluster, for example the one from Deploying the user service with Kubernetes, bring it into Rancher:

The imported cluster's agent connects out to Rancher over HTTPS, so the Rancher hostname must be reachable from that cluster.

6. Manage your deployments

Open the cluster, then Workloads → Deployments, and choose the namespace your service runs in.

Rolling updates replace pods gradually, so a service with at least two replicas and a readiness probe stays online during an update. Always deploy a new, specific image tag (user-service:1.2) rather than overwriting latest, so a rollback returns to a known version.

7. Secure and maintain your Rancher server

• Protect the Kubernetes API. Don't expose port 6443 to the whole internet. Allow it only from addresses that need it, using your server's firewall.
• Use strong admin credentials and create separate Rancher users with limited roles for your team.
• Back up Rancher. The Rancher Backups app can back up its configuration; on k3s, also back up the cluster datastore. Snapshots of the VPS are a useful extra layer, not a replacement.
• Upgrade in order. Upgrade Rancher with helm upgrade, one supported version at a time, and keep Kubernetes within the support matrix.

8. Running Rancher on a Domain India VPS

Domain India VPS plans are KVM virtual servers with full root access, and are self-managed: you install and look after Kubernetes, Rancher and your applications yourself. A VPS can run Docker and Kubernetes. For a Rancher server with a small application cluster on the same node, choose a plan with 8 GB of RAM or more. A 4 GB plan suits k3s with a few services if you manage it with kubectl alone.

If you don't want to run Kubernetes at all, the App Platform builds and runs your app from GitHub or a deploy token, with no servers to manage. For a lighter Kubernetes setup on one VPS, read Lightweight Kubernetes with k3s and Helm charts for beginners.

Frequently asked questions

Ready to run your own cluster? Compare VPS plans, or open a support ticket if you're unsure which size fits your workload.