content/en/docs/v0/operations/configuration/components.md:66 names the right object and never says what removing it costs.
The object part is correct, and worth stating because it differs from every later version. At v0.41.11 the platform chart renders HelmReleases directly from bundles/<name>.yaml in packages/core/platform/templates/helmreleases.yaml; no template renders kind: Package, and there is no internal/operator at all on that line, so no reconciler owns the HelmRelease. kubectl delete hr therefore names exactly what the chart creates, which is not true on v1.0 and later.
What the page never says is that the deletion destroys data. Flux uninstalls the release when the HelmRelease goes away, so any CRD the chart rendered as an ordinary template goes with it and the apiserver cascades every custom resource of those kinds cluster-wide. The platform chart then re-renders the HelmRelease at the next upgrade and the chart reinstalls, so the workloads come back and nothing on screen indicates that anything was lost.
There is a second gap alongside it. On v0 the components are switched off through the bundle-disable key of the cozy-system/cozystack ConfigMap, read at helmreleases.yaml:5, not through disabledPackages. So a reader arriving from a newer page's vocabulary finds neither the field nor the two-step shape, and the page does not connect the two names.
The fix here is a warning and a pointer, not the recipe the newer pages are getting. v0 needs its own short text: what the delete takes with it, and that bundle-disable is the supported way to switch a component off on this line.
content/en/docs/v0/operations/configuration/components.md:66names the right object and never says what removing it costs.The object part is correct, and worth stating because it differs from every later version. At v0.41.11 the platform chart renders HelmReleases directly from
bundles/<name>.yamlinpackages/core/platform/templates/helmreleases.yaml; no template renderskind: Package, and there is nointernal/operatorat all on that line, so no reconciler owns the HelmRelease.kubectl delete hrtherefore names exactly what the chart creates, which is not true on v1.0 and later.What the page never says is that the deletion destroys data. Flux uninstalls the release when the HelmRelease goes away, so any CRD the chart rendered as an ordinary template goes with it and the apiserver cascades every custom resource of those kinds cluster-wide. The platform chart then re-renders the HelmRelease at the next upgrade and the chart reinstalls, so the workloads come back and nothing on screen indicates that anything was lost.
There is a second gap alongside it. On v0 the components are switched off through the
bundle-disablekey of thecozy-system/cozystackConfigMap, read athelmreleases.yaml:5, not throughdisabledPackages. So a reader arriving from a newer page's vocabulary finds neither the field nor the two-step shape, and the page does not connect the two names.The fix here is a warning and a pointer, not the recipe the newer pages are getting. v0 needs its own short text: what the delete takes with it, and that
bundle-disableis the supported way to switch a component off on this line.