Setup On-Prem Kubernetes Cluster
Budget: €10,000 – €20,000 EUR
I want to get a fully functional on-premises Kubernetes cluster running on Debian servers in our own rack. The machines are already racked and cabled; what is missing is a clean installation of Debian, the kube-control plane, worker nodes, networking and basic monitoring so that we can start scheduling workloads straight away.
Scope
• Install the current stable Debian release on each node (I will give you remote IPMI/KVM access).
• Bootstrap the cluster with kubeadm (or an alternative you recommend) including HA control plane, CNI, CSI and basic RBAC.
• Set up a simple storage backend that works in an on-prem environment (NFS, local-PV or similar) and enable metrics-server plus a lightweight dashboard for quick health checks.
• Provide clear, step-by-step documentation so that I can repeat the process on additional nodes later, covering join commands, certificate renewal and backup procedures.
• Finish with a small sample deployment (e.g. nginx) to prove that scheduling, networking and persistent storage are all behaving correctly.
Acceptance
The job is done when kubectl get nodes shows all nodes Ready, a test deployment reaches Running state with working service and persistent volume, and I have the run-book documenting every command you executed.
All work will be done via SSH; no cloud resources are involved. If you have suggestions that improve resilience or simplify maintenance while staying strictly on-prem, feel free to propose them along the way.
Scope
• Install the current stable Debian release on each node (I will give you remote IPMI/KVM access).
• Bootstrap the cluster with kubeadm (or an alternative you recommend) including HA control plane, CNI, CSI and basic RBAC.
• Set up a simple storage backend that works in an on-prem environment (NFS, local-PV or similar) and enable metrics-server plus a lightweight dashboard for quick health checks.
• Provide clear, step-by-step documentation so that I can repeat the process on additional nodes later, covering join commands, certificate renewal and backup procedures.
• Finish with a small sample deployment (e.g. nginx) to prove that scheduling, networking and persistent storage are all behaving correctly.
Acceptance
The job is done when kubectl get nodes shows all nodes Ready, a test deployment reaches Running state with working service and persistent volume, and I have the run-book documenting every command you executed.
All work will be done via SSH; no cloud resources are involved. If you have suggestions that improve resilience or simplify maintenance while staying strictly on-prem, feel free to propose them along the way.