-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Update documentation to reflect removal of --network-plugin
command line parameter in Kubelet 1.24
#39625
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should also update https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors/ to mention that the kubelet no longer needs a --network-plugin
command line argument.
…ne parameter in Kubelet 1.24.
5ade2ea
to
d75820a
Compare
...ks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md
Show resolved
Hide resolved
@@ -314,6 +314,15 @@ This is an incomplete list of things that could go wrong, and how to adjust your | |||
- Mitigates: Node shutdown | |||
- Mitigates: Kubelet software fault | |||
|
|||
{{<note>}} | |||
From Kubernetes 1.24,the kubelet always uses CNI mode for networking. The legacy `--network-plugin` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From Kubernetes 1.24,the kubelet always uses CNI mode for networking. The legacy `--network-plugin` | |
From Kubernetes 1.24, the kubelet is going to use CNI mode for networking. The legacy `--network-plugin` |
...ks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors.md
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
Here's some feedback. I'm sorry it took a while to get round to it - as a project, we're short on maintainer capacity.
{{<note>}} | ||
|
||
From Kubernetes 1.24,the kubelet always uses CNI mode for networking since the legacy `--network-plugin` | ||
command line parameter has been removed from the binary. For more information, refer to [Troubleshooting Clusters](https://kubernetes.io/docs/tasks/debug/debug-cluster/) page. | ||
|
||
{{</note>}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is too early in the page. Make it normal text (not a note callout) and give it a heading.
@@ -314,6 +314,15 @@ This is an incomplete list of things that could go wrong, and how to adjust your | |||
- Mitigates: Node shutdown | |||
- Mitigates: Kubelet software fault | |||
|
|||
{{<note>}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need to be a callout?
Hi @nitishfy, a gentle ping to see if you still have time to address the feedback on this PR? Thanks! |
Hi, I'll mark the changes soon. Thank you! |
Hi @nitishfy . |
@kbhawkey: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes #34756
Closed PR: #34764