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.

Sign up for GitHub

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

Jump to bottom

Clarify custom CNI is not covered by k0s reset #5100

Merged
merged 1 commit into from
Oct 9, 2024
Merged

Clarify custom CNI is not covered by k0s reset #5100

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/reset.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ following:
network interfaces or iptables rules set up specifically for cluster
communication. This is done on a best effort basis. It's recommended that you
reboot the host after a reset to ensure that there are no k0s remnants in the
host's network configuration.
host's network configuration. Custom CNI plugins are not cleaned up.
* Registration with the host's init system: Reverts the registration done by
`k0s install`. After a reset, k0s won't be automatically started when the host
boots.
Expand Down
Loading