You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears the only time a reboot may be necessary, from a sysctl standpoint, is if kubernetes is already running when making changes (to sysctl). If a user is instantiating an RKE2 cluster with rke2-ansible, that reboot doesn't appear to be necessary.
Will research and confirm that the reboot is NOT necessary and then modify and update Ansible code.
Reboot is not necessary unless sysctl is being modified while rke2 is already running. Will add in logic to determine if rke2 is running and create a reboot flag.
It appears the only time a reboot may be necessary, from a sysctl standpoint, is if kubernetes is already running when making changes (to sysctl). If a user is instantiating an RKE2 cluster with rke2-ansible, that reboot doesn't appear to be necessary.
Will research and confirm that the reboot is NOT necessary and then modify and update Ansible code.
@mddamato @aceeric
The text was updated successfully, but these errors were encountered: