Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-evaluate the necessity to reboot a node after making sysctl changes #199

Closed
aleiner opened this issue Apr 11, 2024 · 1 comment · Fixed by #203
Closed

Re-evaluate the necessity to reboot a node after making sysctl changes #199

aleiner opened this issue Apr 11, 2024 · 1 comment · Fixed by #203

Comments

@aleiner
Copy link
Contributor

aleiner commented Apr 11, 2024

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

@aleiner
Copy link
Contributor Author

aleiner commented Apr 12, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant