Skip to content

Latest commit

 

History

History
172 lines (136 loc) · 4.03 KB

README.md

File metadata and controls

172 lines (136 loc) · 4.03 KB
Raw

Proxmox

It was tested on Proxmox version 7.4-3

Local utilities

  • terraform
  • talosctl
  • kubectl
  • yq

Kubernetes addons

  • cilium 1.12.4
  • metrics-server 0.5.0
  • rancher.io/local-path 0.0.19
  • Talos CCM edge, controller: cloud-node. Talos CCM labels the nodes, and approve node server certificate signing request.
  • Proxmox CCM edge, controller: cloud-node-lifecycle. Proxmox CCM deletes the kubernetes node resource if they was deleted in Proxmox.
  • Proxmox CSI Allows you to mount Proxmox disk to the pods.

All deployments use nodeSelector, controllers runs on control-plane, all other on workers.

Steps

  • Prepare - (optional) it uses ansible to configure the proxmox node/cluster.
  • Images - upload the Talos OS image to the Proxmox storage.
  • Init - creates the roles to Proxmox CCM/CSI.
  • Bootstrap cluster

Images

First we need to upload the talos OS image to the Proxmox host machine. If you do not have shared storage, you need to upload image to each machine.

Folow this link README to make it.

Init

Create Proxmox role and account. This credentials will use by Proxmox CCM and CSI.

cd init
terraform init -upgrade
terraform apply

Terraform is not capable of creating account tokens, so you should create them through the web portal instead. Or use this command:

# On the proxmox server.
pveum user token add kubernetes@pve ccm -privsep 0

Bootstrap cluster

Terraform will create the Talos machine config and upload it to the Proxmox server, but only for worker nodes. It will also create a metadata file, which is a very important file that contains information such as region, zone, and providerID. This metadata is used by the Talos CCM to label the nodes and it also required by the Proxmox CCM/CSI.

Contol-plane machine config uploads by command talosctl apply-config, because I do not want to store all kubernetes secrets in proxmox server. Terraform shows you command to launch.

VM config looks like:

# Worker node /etc/pve/qemu-server/worker-11.conf
cpu: host
cicustom: user=local:snippets/worker.yaml,meta=local:snippets/worker-11.metadata.yaml
ipconfig0: ...
net0: ...

Metadata file looks like:

# /var/lib/vz/snippets/worker-11.metadata.yaml
hostname: worker-11
instance-id: 1050
instance-type: 2VCPU-4GB
provider-id: proxmox://cluster-1/1050
region: cluster-1
zone: node1

Worker machine config:

# /var/lib/vz/snippets/worker.yaml
version: v1alpha1
debug: false
persist: true
machine:
  type: worker
...

First we need to define our cluster:

proxmox_domain   = "example.com"
proxmox_host     = "node1.example.com"
proxmox_nodename = "node1"
proxmox_storage  = "data"
proxmox_image    = "talos"

vpc_main_cidr = "172.16.0.0/24"

# We will create one control-plane node on the Proxmox node `node1` (count = 1)
controlplane = {
  "node1" = {
    id    = 500
    count = 1,
    cpu   = 2,
    mem   = 6144,
  },
  "node2" = {
    id    = 520
    count = 0,
    cpu   = 2,
    mem   = 6144,
  },
}

# One web and worker node:
instances = {
  "node1" = {
    web_id       = 1000
    web_count    = 1,
    web_cpu      = 2,
    web_mem      = 4096,
    worker_id    = 1050
    worker_count = 1,
    worker_cpu   = 2,
    worker_mem   = 4096,
  },
  "node2" = {
    web_id       = 2000
    web_count    = 0,
    web_cpu      = 2,
    web_mem      = 4096,
    worker_id    = 2050
    worker_count = 0,
    worker_cpu   = 2,
    worker_mem   = 4096,
  },
}

Create all configs

make init create-config create-templates

Launch the control-plane node

make create-controlplane
# wait ~2 minutes
make create-controlplane-bootstrap

Receive kubeconfig file

make create-kubeconfig