Skip to content

metal3 quickstart: Clarify that storage provider is optional #898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2025
Merged

metal3 quickstart: Clarify that storage provider is optional #898

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions asciidoc/quickstart/metal3.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,11 +77,6 @@ TIP: The steps here can also be fully automated as described in the <<atip-manag

If not already installed as part of the Rancher installation, cert-manager must be installed and running.

A persistent storage provider must be installed. SUSE Storage is recommended but `local-path-provisioner` can also be used for
dev/PoC environments. The instructions below assume a StorageClass has been
https://kubernetes.io/docs/tasks/administer-cluster/change-default-storage-class/[marked as default],
otherwise additional configuration for the Metal^3^ chart is required.

An additional IP is required, which is managed by https://metallb.universe.tf/[MetalLB] to provide a
consistent endpoint for the Metal^3^ management services.
This IP must be part of the control plane subnet and reserved for static configuration (not part of any DHCP pool).
Expand Down