Repository navigation
[release-4.5] docs(alauda-os): correct data retention on Bare Metal host reinstall - #1441
Merged
Merged
Conversation
The provider does not wipe the disks of a Bare Metal host when it reinstalls the host. Scope the "not kept" statements for node-local data to Huawei DCS, Huawei Cloud Stack, and VMware vSphere, and describe what Bare Metal keeps.
Deploying alauda-container-platform with
|
| Latest commit: |
e672543
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://db5b6ea4.alauda-container-platform.pages.dev |
| Branch Preview URL: | https://docs-bm-reinstall-data-reten-ksz4.alauda-container-platform.pages.dev |
chinameok
marked this pull request as ready for review
November 18, 2026 10:35
wgkingk
approved these changes
Nov 18, 2026
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.
Summary
Corrects what the Alauda OS documentation says about data on a Bare Metal host when the host is reinstalled (version upgrade or node replacement).
Expected behavior (given by the product owner, to be confirmed by R&D): When a Bare Metal host is reinstalled, the provider does not wipe its disks. Data on the host's disks is not cleared.
The pages said the opposite: node-local data (
hostPathvolumes, local PersistentVolumes) was "Not kept", and only pool-managed persistent disks, which exist on Huawei DCS, Huawei Cloud Stack, and VMware vSphere only, were listed as an exception. This PR scopes the "not kept" statements to those three providers and adds what Bare Metal keeps. Statements about the IaaS providers are unchanged.Relationship to #1409: that PR plans Bare Metal disks on the same basis (one system disk, no extra disk, upgrade does not wipe disks). This PR aligns the other pages with it. It does not touch #1409's branch or files.
Changes (before → after)
workload_clusters/alauda_os/index.mdx, data tablehostPath, local PV) → "Not kept", for all providers/var/cpaason the system disk and data on other disks, such as raw disks used by LVM Storage (TopoLVM) → "Kept. The provider does not wipe the disks of a host when it reinstalls the host." New row: other data on the Bare Metal system disk → "Not guaranteed", because the OS image is written againupgrade/overview.mdx, data tableNoHostPathWorkloadsexemption procedureupgrade/pre-upgrade.mdx, warning before the provider tabs/var/cpaasis not guaranteed; the preflight still reportshostPathand node-local PVsupgrade/pre-upgrade.mdx, execution host paragraph/root,/home, Core Package) "are lost"upgrade/troubleshooting.mdx, Bare MetalNoHostPathWorkloadsrowworkload_clusters/alauda_os/bare-metal/overview.mdxconfigure/nodes/alauda_os/bare-metal.mdx, "Inventory recycling"reprovisionplan."reprovisionplan … writes the OS image to the system disk again and does not wipe the disks of the host."llms.txt,llmstxt-state.jsonupgrade/overview.mdx,upgrade/pre-upgrade.mdx,upgrade/troubleshooting.mdx,bare-metal/overview.mdx,configure/nodes/alauda_os/bare-metal.mdxFound but not changed
workload_clusters/alauda_os/bare-metal/register_hosts.mdx(disk preparation) andinstall/alauda_os/bare-metal/prerequisites.mdx: the first installation wipes the install disk and staleCOS_*partitions on other disks. This is the one-time registration, not the reinstall, so it is unchanged. See question 4.install/alauda_os/bare-metal/deleting.mdx,workload_clusters/alauda_os/bare-metal/deleting.mdx: the user wipes disks when reclaiming hosts. Consistent with the expectation.upgrade/pre-upgrade.mdxBare Metal tabs andupgrade/troubleshooting.mdx(exemption procedure): theNoHostPathWorkloadscheck still blocks onhostPathvolumes and node-local PVs on Bare Metal. The procedure is real product behavior, so only the reason sentence was changed. See question 2.storage/storagesystem_ceph/installation/immutable_infrastructure_prerequisites.mdx(Bare Metal section): asks the reader to confirm that the provider does not format the OSD device. Consistent with the expectation, but still points to the provider docs for confirmation. See question 5.networking/functions/configure_node_local_dns.mdx: kubelet configuration is lost when nodes are re-provisioned. This is OS configuration, not data.configure/scalability/disk_configuration.mdx: owned by docs(install): add typical installation scenarios and a small Ceph baseline #1409.Please confirm (R&D)
reprovisionplan leave every non-system disk untouched, and is/var/cpaason the system disk preserved? The wording "kept" in rows 1, 2, 3, 6, 7 depends on this. What exactly does the reinstall rewrite on the system disk (OS partitions only)?NoHostPathWorkloadspreflight on Bare Metal blocks the upgrade forhostPathvolumes and node-local PVs, and its original text says the data is "not kept when the host is reinstalled". Why does the check exist if disks are not wiped? Should it stay, be removed for Bare Metal, or have a different reason (for example, the node can be allocated to another host of the pool)?COS_*partition wipe in the first installation also applied at reinstall? If so, a disk withCOS_*labels can be wiped at reinstall.containerdstore, kubelet data, etcd data on control plane hosts?/var/cpaason the system disk the correct example of preserved platform data, and are LVM Storage (TopoLVM) raw disks the correct example for other disks?