no control plane node rolling update is triggered on a change of preRKE2Commands #307
Labels
kind/bug
Something isn't working
needs-priority
Indicates an issue or PR needs a priority assigning to it
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
I observed the following after adding a simple test command (
echo 42 > /tmp/test
) to preRKE2Commands in both my RKE2ControlPlane resource and the RKE2ConfigTemplate resource used for a MachineDeployment.As expected, for the MachineDeployment a node rolling update was triggered.
All the RKE2Config resources for my MD have this test command:
However, for the control plane, no rolling update was triggered.
The RKE2Config resources for the control plane don't have the test command:
The status of the RKE2ControlPlane is fully ready though, showing no sign of any rolling update being in progress:
Of course, the expected behavior would be to have a rolling update being triggered.
Note that a rolling update is properly triggered on a change of, for instance
spec.agentConfig.kubelet.extraArgs
.(The title of this issue is about "a change of preRKE2Commands", because I didn't try to be exhaustive in this bug report, but we observed the issue on other fields and it's likely not specific to preRKE2Commands)
The text was updated successfully, but these errors were encountered: