whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
* Fixed the incorrect parameter of specifying the CRI endpoint for kubelet

Corrected the parameter of '--container-runtime-path-endpoint' with '--container-runtime-endpoint'

* Corrected Default CNs

Fixed the incorrect Default CNs for apiserver-etcd-client.crt and apiserver-kubelet-client.crt
This commit is contained in:
bogard1203
2019-11-28 13:17:03 +08:00
committed by Kubernetes Prow Robot
parent def4eade2f
commit 68e836b267
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/production-environment/tools/kubeadm/kubelet-integration.md
+1 -1
View File
@@ -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.