Open paddy-hack opened 3 weeks ago
With v1.5.9 the
rke util get-state-file
command succeeds.
Clarification: This holds for a v1.5.9 deployed cluster. Using v1.5.9 against a v1.5.10 deployed cluster rke util get-state-file
fails. This is because the full-cluster-state
ConfigMap that the command looks for is no longer present.
RKE version:
Docker version: (
docker version
,docker info
preferred)Operating system and kernel: (
cat /etc/os-release
,uname -r
preferred)Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
cluster.yml file:
Steps to Reproduce:
Results:
With
v1.5.9
therke util get-state-file
command succeeds.\ The test results (per scenario 2) for the issue that adds therke util
commands indicate that the intent is for the command to succeed.Some further testing shows that with
v1.5.10
the command succeeds ifkube_config_cluster.yml
is present.This behavioral change broke my CI/CD setup :sob:
The change is introduced by the "fix" for CVE-2023-321-91. The release notes mention it but that did not ring a bell for me and I spent the morning figuring out what had happened :tired_face:
Thinking of provisioning my CI/CD job with a copy of
kube_config_cluster.yml
to make them work again.\ Obviously, that file cannot be added to thegit
repository I use to maintain my clusters.Submitting this in the hope it helps someone running into the same :bow: