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

Fixed the incorrect parameter of specifying the CRI endpoint for kubelet and corrected Default CNs #17839

Merged
merged 2 commits into from
Nov 28, 2019
Merged

Fixed the incorrect parameter of specifying the CRI endpoint for kubelet and corrected Default CNs #17839

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b36f17d
Fixed the incorrect parameter of specifying the CRI endpoint for kubelet
bogard1203 Nov 27, 2019
fe7afd1
Corrected Default CNs
bogard1203 Nov 27, 2019
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 content/en/docs/setup/production-environment/tools/kubeadm/kubelet-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ networking, or other host-specific parameters. The following list provides a few
- Depending on the CRI runtime your cluster uses, you may need to specify different flags to the kubelet.
For instance, when using Docker, you need to specify flags such as `--network-plugin=cni`, but if you
are using an external runtime, you need to specify `--container-runtime=remote` and specify the CRI
endpoint using the `--container-runtime-path-endpoint=<path>`.
endpoint using the `--container-runtime-endpoint=<path>`.

You can specify these flags by configuring an individual kubelet's configuration in your service manager,
such as systemd.
Expand Down