feat: add bare-metal K3s deployment guide - #397
Conversation
berendt
left a comment
berendt
left a comment
There was a problem hiding this comment.
I would prefer it if AI-generated content were labeled as such and remained in draft form until it has been fully tested. We should avoid using versions that are (soon to be) EOL.
Add a complete deployment guide for SCS-compliant bare-metal K3s clusters, addressing the current documentation gap (which focuses on Cluster API + OpenStack). Content: - Architecture overview (3-node K3s with Ceph, HAProxy, Flannel) - Hardware/software prerequisites - Step-by-step deployment instructions - SCS compliance verification (SCS-0210, SCS-0211, SCS-0214, SCS-0217) - Troubleshooting guide Reference implementation: 3-node bare-metal K3s cluster (one master, two workers) — SCS-0210/0211/0214/0217 checks PASS. Related: Standards supplement 'SCS-0217 bare-metal K3s implementation notes' submitted to SovereignCloudStack/standards. Signed-off-by: Tobias Weiss <tobias-weiss-ai-xr@users.noreply.github.com>
c7e078c to
aa2d94b
Compare
|
Thanks for the review, @berendt. Regarding the request to label this guide as AI-generated content: I understand the motivation behind transparency, but to be honest I feel that singling out content simply because of the tooling used to author it is a bit discriminatory. What matters in a technical contribution is its quality, accuracy and how well it is tested — not the process that produced it. A human-written, untested guide is arguably riskier than an AI-assisted one that has been verified end-to-end against a real cluster. I would advocate for adjusting the contribution guidelines/regulation so that the requirement focuses on verification and testing status (which we fully agree with — that is why this content should be kept in draft until validated - my bad), rather than on how the text was generated. Happy to align the document with whatever convention the project prefers. I am amending the PR now to address the points: OS/software versions brought up to currently maintained releases (Ubuntu 24.04, Debian 13, Ansible 2.19, MetalLB v0.16.0, HAProxy Ingress v3.2.13), the broken HAProxy manifest URL, and the MetalLB install source. |
- Label as [graphwiz.AI generated content], draft status - Update to currently maintained software: Ubuntu 24.04 LTS, Debian 13, Ansible core 2.19+, MetalLB v0.16.0, HAProxy Ingress v3.2.13 - Fix broken HAProxy Ingress manifest URL (v2.8.3 release download 404ed; use the v3.2.13 deploy manifest) and MetalLB install source - Use sudo for the K3s install script (non-root best practice) Signed-off-by: Tobias Weiss <tobias-weiss-ai-xr@users.noreply.github.com>
|
Hi @tobias-weiss-ai-xr and thank you for this contribution. Could you please clarify which parts of this contribution were tested and verified by you and which parts were just generated and are completely untested so far? |
3 participants
Add a complete deployment guide for SCS-compliant bare-metal K3s clusters, addressing the current documentation gap (which focuses on Cluster API +
OpenStack).
Content:
Reference implementation: 3-node bare-metal K3s cluster (one master, two workers) on Ubuntu 24.04 LTS — SCS-0210/0211/0214/0217 checks PASS.
Related: Standards supplement SCS-0217 bare-metal K3s implementation notes (SovereignCloudStack/standards #1267).
Note: AI-generated content, kept in draft until fully reviewed/tested.