Can Api definitions, version definition, enable_unprivileged_ports and enable_unprivileged_icmp definitions explain why rke2-canal pods keep restarting after a node reboot ? #5079
Unanswered
marcredhat
asked this question in
Q&A
Replies: 1 comment
-
I can't provide any insight into that user's motivations in customizing their containerd config template to modify those values. That shouldn't be necessary, as they are enabled by default if the kernel supports it. I suspect their problems may have been self-infliced, as their template does not appear to actually contain any templating values, but is instead just a very basic flat config file.
If you're having a specific problem with your nodes, please create a new issue and fill out the issue template. If you want to discuss blog posts, that might be better handled in a discussion, instead of an issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The last part of
https://medium.com/@ozkanpoyrazoglu/troubleshooting-kube-proxy-and-rke2-canal-pods-restart-loop-lessons-from-upgrading-ubuntu-20-04-7ac6107c6475
seems to suggest that
not setting
Api definitions, version definition, enable_unprivileged_ports and enable_unprivileged_icmp definitions
can explain why rke2-canal pods keep restarting after a node reboot.
Configs shown at #3385 also set
enable_unprivileged_ports
andenable_unprivileged_icmp
.Could you please provide the details on the role of the above flags?
@brandond
Beta Was this translation helpful? Give feedback.
All reactions