Ditto for the config yaml on each server node what happens i rancher-users #rke2

Title

broad-farmer-70498

09/01/2022, 1:53 PM

Ditto for the config.yaml on each server node, what happens if they don’t match exactly on things like addons, kubelet args etc?

victorious-analyst-3332

09/01/2022, 4:09 PM

they can technically be different, but it will lead to the nodes behaving differently 🤷

broad-farmer-70498

09/01/2022, 4:11 PM

kubelet-arg was probably a bad example, as that should be tweaked/set on the agents as well

victorious-analyst-3332

09/01/2022, 4:13 PM

examples of what I’ve tweaked in the past for things like metrics scraping from outside the cluster

etcd-expose-metrics: true
kube-controller-manager-arg:
  - "bind-address=0.0.0.0"
kube-proxy-arg:
  - "metrics-bind-address=0.0.0.0:10249"

broad-farmer-70498

09/01/2022, 4:13 PM

yeah, I'm mostly referring to the things that are 'cluster' options like

cni: none

what happens if one of the server nodes doesn't have that and another does or they have different values etc? or should I only set that on the bootstrap node and then have quite minimal configs for all the other servers similar to the agent configs

victorious-analyst-3332

09/01/2022, 4:15 PM

those values aren’t propagated that I know of, so you’ll need them on all nodes that you plan to interact with in that way

things like

cni: none

are part of the rancher cluster config that get automatically pushed down to the clusters I believe

broad-farmer-70498

09/01/2022, 4:16 PM

so that's a 'last man wins' scenario as well?

victorious-analyst-3332

09/01/2022, 4:17 PM

no idea in that scenario

I think best practice is to make sure they match to prevent issues if something goes offline

👍 1

20 Views

#rke2 Join Slack