You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c6c4e9c
Browse filesBrowse the repository at this point in the historyBrowse files
docs(kubernetes): make the Proxmox VE substrate enablement followable
The page used the capmox token in step 1 and created it in step 2, and
showed bundles.enabledPackages as a values fragment without saying how to
set it. Order the steps so each uses only what exists, give the Package
patch, and add the CCM Secret the example references. Link the page from
the deployment guide, which had no path to it.
Carry the four v1.7 corrections from #782 to next/.
v1.7.0 runs proxmox-cloud-controller-manager:v0.15.0, a tag that now
resolves to a build that panics at start, so the v1.7 copy gets the image
override until the backport in cozystack/cozystack#5150 is released.
Assisted-by: LLM
Signed-off-by: Marian Koreniuk <moriarti@cp.if.ua>
There are two ways to use Cozystack with an existing Proxmox VE cluster, and they can be combined:
51
+
52
+
- Run the Cozystack cluster itself in Proxmox VE VMs: follow the [generic installation path](#generic-installation-path), treating the VMs like any other machines. Set the VM CPU type to `host` if tenants will run KubeVirt VMs on them.
53
+
- Run the workers of tenant Kubernetes clusters as VMs on Proxmox VE instead of KubeVirt: [enable the Proxmox VE substrate]({{% ref "/docs/next/kubernetes/proxmox-substrate" %}}). This is opt-in and experimental.
54
+
48
55
## Upgrading and Post-deployment Configuration
49
56
50
57
After you've deployed a cluster, proceed to the [Cluster Administration]({{% ref "/docs/next/operations" %}}) section for
@@ -269,7 +295,7 @@ are plainly present on the template.
269
295
kubectl -n tenant-a get cluster,proxmoxcluster,machinedeployment,machine
270
296
kubectl -n tenant-a get proxmoxmachines -o custom-columns='NAME:.metadata.name,VMID:.spec.virtualMachineID,NODE:.status.proxmoxNode,IP:.status.ipAddresses.net0.ipv4,STATE:.status.vmStatus'
271
297
kubectl -n tenant-a get inclusterippools,ipaddresses.ipam.cluster.x-k8s.io
272
-
kubectl -n tenant-a get deploy px-pccm px-pcsi-controller
298
+
kubectl -n tenant-a get deploy kubernetes-px-pccm kubernetes-px-pcsi-controller
273
299
274
300
# tenant cluster
275
301
kubectl --kubeconfig <tenant kubeconfig> get nodes -o wide
@@ -319,8 +345,8 @@ MachineHealthCheck.
319
345
| every API call returns 501 | `PROXMOX_URL` already contains `/api2/json` | use bare `https://host:8006` |
320
346
| `found 0 VM templates with tags ...` | `templateTags` ≠ the template's tag set | list every tag, exactly |
321
347
| Machine `VMProvisioned=True`, node never joins, no CSR | workers cannot reach the tenant apiserver LoadBalancer IP, or no reachable `dnsServers` | fix L3 / DNS |
322
-
| Nodes `Ready` but keep `uninitialized` taint, pool `ScalingUp` forever | CCM not running or crash-looping | `kubectl -n <tenant ns> logs deploy/<cluster>-pccm` |
323
-
| CSI node plugin `CrashLoopBackOff`, `Failed to get region or zone` | CCM has not labelled the node yet | wait for the CCM; the CSI release depends on it |
348
+
| Nodes `Ready` but keep `uninitialized` taint, pool `ScalingUp` forever | CCM not running or crash-looping | `kubectl -n <tenant ns> logs deploy/kubernetes-<cluster>-pccm` |
349
+
| CSI node plugin `CrashLoopBackOff`, `Failed to get region or zone` | CCM has not labelled the node yet | wait for the CCM |
324
350
| VM reboots every ~70 min, never joins | template built from the bare-metal `nocloud` image | rebuild with `hack/proxmox-talos-template.sh` |
325
351
| `TalosConfigTemplate.Spec is immutable` | apiserver address changed on an existing cluster | delete the template; the reconcile Job recreates it |
326
352
| capmox stuck at `Waiting for Cluster Controller to set OwnerRef` | `cluster.x-k8s.io/managed-by` annotation on the `ProxmoxCluster` | not expected from the chart; report it |
There are two ways to use Cozystack with an existing Proxmox VE cluster, and they can be combined:
51
+
52
+
- Run the Cozystack cluster itself in Proxmox VE VMs: follow the [generic installation path](#generic-installation-path), treating the VMs like any other machines. Set the VM CPU type to `host` if tenants will run KubeVirt VMs on them.
53
+
- Run the workers of tenant Kubernetes clusters as VMs on Proxmox VE instead of KubeVirt: [enable the Proxmox VE substrate]({{% ref "/docs/v1.7/kubernetes/proxmox-substrate" %}}). This is opt-in and experimental.
54
+
48
55
## Upgrading and Post-deployment Configuration
49
56
50
57
After you've deployed a cluster, proceed to the [Cluster Administration]({{% ref "/docs/v1.7/operations" %}}) section for
| every API call returns 501 | `PROXMOX_URL` already contains `/api2/json` | use bare `https://host:8006` |
321
361
| `found 0 VM templates with tags ...` | `templateTags` ≠ the template's tag set | list every tag, exactly |
322
362
| Machine `VMProvisioned=True`, node never joins, no CSR | workers cannot reach the tenant apiserver LoadBalancer IP, or no reachable `dnsServers` | fix L3 / DNS |
363
+
| CCM in `CrashLoopBackOff`, `panic: version string "0.15.0"` | the image v1.7.0 ships | set the image as in step 4 |
323
364
| Nodes `Ready` but keep `uninitialized` taint, pool `ScalingUp` forever | CCM not running or crash-looping | `kubectl -n <tenant ns> logs deploy/kubernetes-<cluster>-pccm` |
324
365
| CSI node plugin `CrashLoopBackOff`, `Failed to get region or zone` | CCM has not labelled the node yet | wait for the CCM |
325
366
| VM reboots every ~70 min, never joins | template built from the bare-metal `nocloud` image | rebuild with `hack/proxmox-talos-template.sh` |
0 commit comments