Conversation
|
@teasonia Thanks for your contribution! The modification needs to be backwards compatible. You should check |
|
Basically, this is what's needed; How do I get that into this PR? |
|
As far as I know the versioncmp is not needed. This command should work from at least version 1.18 and is a basic command. So it should work for all version. Regarding the change, it would be a good idea to update the manifests/kubeadm_init.pp also. |
|
This module is broken on >=1.32 without the changes in this MR. Can we merge this MR? |
|
@yoshz No, we can't merge it. The code needs to be rebased. |
baf7238 to
73d8e4d
Compare
73d8e4d to
ebab241
Compare
|
Hello all! I just rebased this again and ran the basic CI. Unfortunately, the acceptance tests seem to be broken with an underlying provisioning issue (unrelated to this PR) so testing can't go further. That underlying provisioning issue will need to be resolved so we can get acceptance tests working again before being able to move further. That said, there was some discussion here about needing a version check for which command to run. Am I correct in understanding that the current change is backwards compatible? |
Summary
This commit corrects the node check in kubeadm_join.pp to work correctly with Kubernetes 1.32 and later versions. The previous check relied on kubelet having permissions to list all nodes, which is no longer the case. The updated check uses
kubectl get nodes <node_name>instead.Additional Context
After upgrading kubernetes to version 1.32, applying puppet on existing nodes results in the node being added again. This happens because getting all nodes causes an error.
Getting its own node happens without errors