Download and Prepare KVM Image:
Download the Ubuntu KVM image and prepare it as a template on Proxmox.
Create and Clone Templates:
Set up initial VM templates for three master nodes, two worker nodes, and one additional node (referred to as “King”), which seems to be the management or control node for the cluster.
Disk and RAM Resizing:
Resize the disk space and RAM for worker nodes to meet the requirements of your applications or services running on Kubernetes.
Network Configuration:
Configure static IPs for all nodes to ensure consistent internal communication, possibly using a router like MikroTik for DHCP reservations or static IP assignments.
Kubernetes Setup via Script:
Fork and modify the deployment script from a GitHub repository (in this case, godevgod/JimsGarage), customizing the Kubernetes deployment to fit your network and cluster configuration.
Install Helm and Rancher:
Install Helm, a package manager for Kubernetes, which simplifies the deployment of applications and services on your cluster.
Use Helm to deploy Rancher, a powerful Kubernetes management tool, which will allow you to manage your cluster more easily through a user-friendly interface.
Final Configuration:
After deploying Rancher, expose it as a service in your network, allowing you to access the Rancher UI via a web browser.
Set up administrative accounts and necessary permissions within Rancher to manage your cluster.
This setup, as you’ve noted, can take varying amounts of time depending on hardware capabilities and potential troubleshooting needs. Your detailed step-by-step approach is excellent for ensuring all bases are covered, but be prepared for potential issues that may require adjustments to configurations, especially around network settings and script customizations.
https cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-disk-kvm.img
paste download url and and hit query then download it
so go to host terminal
qm create 5000 –memory 4096 –core 4 –name ubuntu-cloud –net0 virtio,bridge=vmbr0
cd /var/lib/vz/template/iso/
qm importdisk 5000 jammy-server-cloudimg-amd64-disk-kvm.img local-lvm
qm set 5000 –scsihw virtio-scsi-pci –scsi0 local-lvm:vm-5000-disk-0
qm set 5000 –ide2 local-lvm:cloudinit
qm set 5000 –boot c –bootdisk scsi0
qm set 5000 –serial0 socket –vga serial0
qm resize 5000 scsi0 +18G for all because begin start by 2GB only
qm resize 242 scsi0 +80G for worker add hdd size
qm resize 243 scsi0 +80G
clone each machine to
clone king machine and then
3Master1+Master2+Master3,+Worker1+Worker2
Go king machine terminal then
after start open all machine then must mask static ip for each machine or fix ip now use mikrotik
edit script before that must fork this project
godevgod/JimsGarage
then edit Kubernetes/K3S-Deploy
file k3s.sh
see in clip change this
Set the IP addresses of the master and work nodes according to your own ip range
master1=10.1.1.246
master2=10.1.1.245
master3=10.1.1.244
worker1=10.1.1.243
worker2=10.1.1.242
user=ubuntu
Set the virtual IP address (VIP)
vip=10.1.1.50
lbrange=10.1.1.60-10.1.1.80
then copy
id_rsa
id_rsa.pub
to home directory of king directory
and copy k3s.sh and chmod all to 764 or 777 id_rsa id_rsa.pub k3s.sh
then run ./k3s.sh
and hope it success if it not error so you go to right path
after that check 10.1.xx.60 if nginx open so it mean kube install be done
so move to next step
Prepare to install Rancher
install helm from helm.sh to run auto install rancher
goto Helm | Installing Helm
replace https real
$ curl -fsSL -o get_helm.sh HTTPS … raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3
$ chmod 700 get_helm.sh
$ ./get_helm.sh
[ad_2]
source
