Repository navigation
docs(kubernetes): describe the Proxmox VE substrate for tenant clusters - #761
Open
Marian Koreniuk (themoriarti) wants to merge 2 commits into
Open
Marian Koreniuk (themoriarti) wants to merge 2 commits into
Marian Koreniuk (themoriarti) wants to merge 2 commits into
Conversation
Marian Koreniuk (themoriarti)
requested review from
Andrei Kvapil (kvaps),
Timofei Larkin (lllamnyp),
myasnikovdaniil and
Timur Tukaev (tym83)
as code owners
October 20, 2026 09:27
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
myasnikovdaniil
added a commit
that referenced
this pull request
Oct 30, 2026
v1.7.0 ships the Proxmox VE substrate for tenant Kubernetes workers and its release notes lead with it, yet the v1.7 docs have no page for it: #761 adds one to next/ only. The page is #761's with the rewrite release_next.sh applies, checked against the v1.7.0 tag. Four things did not hold there and are corrected in this copy: - KubernetesNodes has no replicas field; a pool is sized by minReplicas and maxReplicas, which the tag's own Proxmox e2e manifest sets. - The CCM and CSI controller Deployments are <release>-pccm and <release>-pcsi-controller, and a Kubernetes release is named kubernetes-<name>, so the cluster px runs kubernetes-px-pccm. The verify command and the troubleshooting row now name those. - bundles.enabledPackages is read only from the platform values on the cozystack.cozystack-platform Package; no cozystack ConfigMap feeds it. - The CSI HelmRelease depends on the tenant's Cilium release, not on the CCM, which is a plain Deployment, so the troubleshooting fix only says to wait for the CCM. next/ stays with #761. Assisted-By: LLM Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
myasnikovdaniil
added a commit
that referenced
this pull request
Oct 30, 2026
v1.7.0 ships the Proxmox VE substrate for tenant Kubernetes workers and its release notes lead with it, yet the v1.7 docs have no page for it: #761 adds one to next/ only. The page is #761's with the rewrite release_next.sh applies, checked against the v1.7.0 tag. Four things did not hold there and are corrected in this copy: - KubernetesNodes has no replicas field; a pool is sized by minReplicas and maxReplicas, which the tag's own Proxmox e2e manifest sets. - The CCM and CSI controller Deployments are <release>-pccm and <release>-pcsi-controller, and a Kubernetes release is named kubernetes-<name>, so the cluster px runs kubernetes-px-pccm. The verify command and the troubleshooting row now name those. - bundles.enabledPackages is read only from the platform values on the cozystack.cozystack-platform Package; no cozystack ConfigMap feeds it. - The CSI HelmRelease depends on the tenant's Cilium release, not on the CCM, which is a plain Deployment, so the troubleshooting fix only says to wait for the CCM. next/ stays with #761. Assisted-By: LLM Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
myasnikovdaniil
added a commit
that referenced
this pull request
Oct 30, 2026
) The v1.7 docs were cut from `next/` in #780 while several docs PRs about v1.7.0 behaviour were still open against `next/` only, so `/docs/v1.7/` and the stable `/docs/` copy miss them. This adds their content to `content/en/docs/v1.7/`, checked against the v1.7.0 tag. Every page is the source PR's `next/` file with the same `/docs/next/` rewrite that `hack/release_next.sh` does, except where noted. - #763 - #747, hand-merged after `networking.kubeovn.MASTER_NODES` because main got the `networking.encryption.enabled` row after its base - #761, with four corrections below - #762 - #766 - #764, the HTTPCache section of the upgrade guide, in both `next/` and `v1.7/` on top of the fixes from #781. I'm not carrying 764 further, this PR takes over its content. Four lines of the Proxmox page are wrong for v1.7.0 and are fixed in the v1.7 copy only. `replicas: 2` in the KubernetesNodes example is now `minReplicas: 2` and `maxReplicas: 2`, there is no `replicas` field. The CCM and CSI controller Deployments are `kubernetes-<cluster>-pccm` and `kubernetes-<cluster>-pcsi-controller`. `bundles.enabledPackages` is set on the `cozystack.cozystack-platform` Package, no ConfigMap feeds it. The CSI release depends only on the tenant Cilium release, not on the CCM, so I cut that clause. The `next/` copy in 761 needs the same fixes. The `next/` side of 763, 747, 761, 762 and 766 and the `v1.6/` side of 763, 762 and 766 stay in their own PRs, so they still merge without conflicts with this one. Nothing generated is committed, the stable `/docs/` copies are built from `v1.7/` at build time. Hugo production and preview builds, `hack/check-i18n.sh` and a link and anchor check of every changed page pass locally, with the same Hugo warnings as main.
Add a page under Managed Kubernetes for substrate: proxmox, the opt-in option that runs the workers of a tenant cluster on an external Proxmox VE cluster through capmox: what runs where, the support matrix, enabling the packages, Proxmox user/token/pool setup with the privileges the charts document, the Talos template script, Kubernetes and KubernetesNodes values, verification, the isolation model, limitations and troubleshooting. Assisted-by: LLM Signed-off-by: Marian Koreniuk <moriarti@cp.if.ua>
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 cozystack#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>
Marian Koreniuk (themoriarti)
force-pushed
the
docs/proxmox-substrate
branch
from
October 30, 2026 20:25
78e5af5 to
c6c4e9c
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Adds
docs/next/kubernetes/proxmox-substrate.md: an operator page forsubstrate: proxmoxon thekubernetes/kubernetes-nodesapplications (cozystack/cozystack#4087, #4088, #4089, #4742), which ships opt-in inv1.7.0-rc.1.The page covers:
main, Proxmox VE 9.2.x verified, capmox v0.7.7);cozystack.capi-provider-infra-proxmoxand thecapmox-configSecret, with the three mistakes the chart comments call out (PROXMOX_URLwithout/api2/json, full token id, rotation needs a restart);kuberneteschart README;hack/proxmox-talos-template.shand why not from the bare-metalnocloudimage;KubernetesandKubernetesNodesexamples with theproxmox.*values as documented invalues.yaml;It is placed under Managed Kubernetes because
substrateis a property of a tenant cluster; the provider guides under Install are about hosting Cozystack itself.The steps are ordered so each uses only what already exists: capmox token,
capmox-configSecret, then thekubectl patchon the Platform Package.install/_index.mdgets a Proxmox VE section, since the page was not reachable from the deployment guide.v1.7
The page reached
v1.7/through #782, which also corrected four lines; this carries those tonext/and applies the changes above to both copies.The
v1.7/copy also warns about the CCM image: v1.7.0 runsproxmox-cloud-controller-manager:v0.15.0, and that tag now resolves tosha256:d81702998ae1…, which panics at start (version string "0.15.0" doesn't match expected regular expression). The warning gives akubectl set imageto v0.16.1 until cozystack/cozystack#5150 is released; remove it then.What it does not do
Checks
packages/apps/kubernetes{,-nodes}/values.yamland thekuberneteschart README onmain(aed7fa896).docs/Usage.md; the CCM/CSIregionmeaning matchesproxmox-cloud-controller-managerdocs/config.md.KubernetesandKubernetesNodesexamples render withhelm templateon thev1.7.0charts. The Deployment names come from that render.v0.15.0tag panics,v0.16.1starts. The substrate itself has not been run live on the v1.7.0 tag.Related: cozystack/cozystack#3481, cozystack/community#98, #741.