This message was deleted.
# general
a
This message was deleted.
b
hi, i have just found this doc https://ranchermanager.docs.rancher.com/pages-for-subheaders/k3s-hardening-guide#reference-hardened-k3s-template-configuration and trying to customize kube-api, i believe it could help u as well. After modifications, all pods will be restarted by rancher, no need to do this manually
l
Thanks, I'm new here so have some questions about the wiki you gave. In wiki page, it seems there is a k8s resource "kind: Cluster". It supports rkeConfig in its yaml. Once I changed any configurations there, this kind of resource will automatically restart all pods to adopt the changes right? My question is, where does "kind: Cluster" comes from? is it a customized resource which will write the changes in yaml file and restart pods by itself? If that's the case, then what I really ask is, does RKE2 itself support dynamic config changes. That means, once I update configurations somewhere, pods can adopt the changes automatically without pods restart
Also after I changed the value in rkeConfig, how RKE2 services like kube-apiserver/kube-controller adopt the changes without restart? What's the mechanism behind? Does RKE2 has some restful API to support config change without restart? Thanks