docs: import the operator guides that lived in the cozystack repo - #648
docs: import the operator guides that lived in the cozystack repo#648myasnikovdaniil wants to merge 1 commit into
Conversation
Four guides had been written into cozystack/cozystack under docs/ as part of the feature PRs that added the code, and never routed anywhere a user would look. They are operator-facing how-tos with no reason to sit in the source tree, so move them here, into both next/ and v1.6/. New pages: - virtualization/vgpu.md — NVIDIA vGPU on the vgpu variant: the two host driver models, building the vGPU Manager image, SR-IOV profile assignment, DLS licensing, the L40S profile table, OS support. - operations/troubleshooting/gpu-operator-host-driver.md — the passthrough variant refusing to bind vfio-pci when the host already carries an apt-installed driver. This was a 120-line troubleshooting runbook wedged inside the vGPU guide; it is its own problem and now its own page. - networking/vm-external-vlan.md — bridging a VM onto a physically routed VLAN, and why macvlan cannot work with KubeVirt bridge binding. The CNI-plugin staging contract that shared that document stays in the cozystack repo, as packages/system/multus/README.md, because a bats suite asserts its prose against the Dockerfile and the manifest. - networking/hubble.md — enabling Hubble, plus the four dashboards Cozystack ships for it. Stale and PR-shaped content dropped rather than carried over: a "Last verified ... this PR's vgpu variant" stamp, and two claims that the container variant was unmerged (it landed in cozystack#2766 last June, so the runbook now points at it as the no-purge alternative). NVIDIA/k8s-driver-manager#191 was re-checked and is still open. Two corrections to existing pages while wiring them up. virtualization/ gpu.md said vGPU "uses mediated devices (mdev)", which is only true up to Ampere — Ada Lovelace and newer use SR-IOV virtual functions. networking/hubble.md notes that the dashboards are provisioned from dashboards-infra.list, which renders only for tenant-root and cozy-monitoring, so they appear in the platform Grafana and not in a tenant's own. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 56 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (12)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
These four guides were written into cozystack/cozystack under
docs/inside the feature PRs that added the code, and never routed anywhere a user looks. They are operator facing how-tos with no reason to sit in the source tree, so I moved them here, into bothnext/andv1.6/.New pages
virtualization/vgpu.md- NVIDIA vGPU on the vgpu variant: two host driver models, building the vGPU Manager image, SR-IOV profile assignment, DLS licensing, L40S profile table, OS support.operations/troubleshooting/gpu-operator-host-driver.md- passthrough variant refusing to bind vfio-pci when the host already carries an apt installed driver. This was a 120 line runbook wedged inside the vGPU guide, it is its own problem so it gets its own page.networking/vm-external-vlan.md- bridging a VM onto a physically routed VLAN, and why macvlan does not work with kubevirt bridge binding.networking/hubble.md- enabling hubble, plus the four dashboards cozystack ships for it.Dropped stale content instead of carrying it over: a "Last verified ... this PR's vgpu variant" stamp, and two claims that the container variant is unmerged (it landed in cozystack/cozystack#2766 last June, so the runbook points at it as the no-purge alternative now). Rechecked NVIDIA/k8s-driver-manager#191, still open.
Two fixes to existing pages while wiring the links.
virtualization/gpu.mdsaid vGPU uses mediated devices, that is only true up to Ampere, Ada Lovelace and newer use SR-IOV virtual functions. And the hubble dashboards come fromdashboards-infra.list, which renders only for tenant-root and cozy-monitoring, so they appear in the platform grafana and not in a tenant's own.The CNI plugin staging contract that shared the vm-external-vlan document stays in cozystack/cozystack as
packages/system/multus/README.md, because a bats suite asserts its prose against the Dockerfile and the manifest. Deletion of the originals is a separate PR there, i'll link it once it is open.