Files
cozystack/packages
Myasnikov Daniil 3c519c7d6f chore(kubernetes-nodes): name a remedy that works in the foreign-pool error
When a MachineDeployment named after the pool already belongs to
another Helm release, the render failed with advice to remove the pool
from the parent Kubernetes CR's nodeGroups. The parent renders no
worker pool any more, so that edit cannot clear the conflict. The cases
that do reach this guard are a pool migration 56 left with the
cluster's release and two pools whose <cluster>-<pool> split builds
the same object name; the message now says so and points at renaming
the pool or removing the other one.

The foreign-owner branch had no test, so a case pins it, including the
message, against a MachineDeployment owned by the cluster's release.

Assisted-by: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
2026-11-12 18:03:43 +05:00
..