Closed rbrtbnfgl closed 1 month ago
I originally misinterpreted this configuration based on the validation steps provided - have confirmed though all active branches with cni: non on the server still correctly cluster up with windows agents
Validated using COMMIT=5d8fe2c976335f712ca3ff8f1b1bd4684d703d2f
Infrastructure
Node(s) CPU architecture, OS, and version:
Linux 6.4.0-150600.23.17-default x86_64 GNU/Linux PRETTY_NAME="SUSE Linux Enterprise Server 15 SP6"
Cluster Configuration: note nodes are NotReady waiting for CNI installation due to "none"
NAME STATUS ROLES AGE VERSION
ec2amaz-fslbpgh NotReady <none> 2m1s v1.28.14
ip-3-3-3-17 NotReady control-plane,etcd,master 14m v1.28.14+rke2r1
Config.yaml:
node-external-ip: 3.3.3.42
token: YOUR_TOKEN_HERE
write-kubeconfig-mode: 644
debug: true
cni: none
Backport for #6819