https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rke2
a
This message was deleted.
c
That looks fine. You just need to also specify ipv6 addresses for everything. What sort of problem are you running into?
n
The "calico-system" pods are going into "CrashLoopBackOff" if I add the ipv6 addresses for "cluster-cidr" & "service-cidr" fields as below,
Copy code
cluster-cidr: "10.42.0.0/16,2001:cafe:42:0::/56"
service-cidr: "10.43.0.0/16,2001:cafe:42:1::/112"
I came across this github link that uses multiple fields like "node-ip", "kube-apiserver-arg" & "kube-controller-manager-arg", https://github.com/rancher/rke2/issues/870 Kindly let me know if I need to add any of those fields in "config.yaml" files of both server and agent nodes.
@creamy-pencil-82913 any suggestions on this please
b
You should also specify a dual-stack node-ip
Kubelet is only capable of detecting one IP from your node
n
I hope "node-ip" should be assigned with IPV4 and IPV6 addresses of the host, am I correct?
b
yes
n
should this be added in the config.yaml file of both server and agent configurations?
b
let me give you an example
👍 1
Copy code
write-kubeconfig-mode: 644
token: "secret"
node-ip: 10.0.10.40,2a02:d011:a6f:4699:58c6:8609:a6d5:d1cb
cluster-cidr: 10.42.0.0/16,2001:cafe:42:0::/56
service-cidr: 10.43.0.0/16,2001:cafe:43:1::/112
where 
10.0.10.40
and 
2a02:d011:a6f:4699:58c6:8609:a6d5:d1cb
are the ips of the main interface of my node
If you want to add workers, they should include their node-ip parameter in their config too
the cluster-cidr and service-cidr is only needed for the server
n
Thanks much for the detailed explanation @bland-account-99790
b
Example for agent:
Copy code
server: "<https://10.0.10.40:9345>"
token: "secret"
node-ip: 10.0.10.41,2a05:d111:c6f:4a99:e30:945e:a70f:717e
👍 1
@narrow-noon-75604 Thanks for reporting this, I noticed that our rke2 docs are not explaining this. Something to improve
💯 1
158 Views
Open in Slack
PreviousNext
Powered by