kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

update cloud-provider-refactoring.md and kubelet-cri-logging.md

This commit is contained in:
陈宏 2017-10-27 09:30:59 +08:00
parent 2114936653
commit 5e3a738bd4
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/design-proposals/cloud-provider/cloud-provider-refactoring.md
View File

@ -133,7 +133,7 @@ This is the only step that is different in the upgrade process. In order to comp
kubectl apply -f cloud-controller-manager.yml kubectl apply -f cloud-controller-manager.yml
``` ```
This will start the cloud specific controller manager in your kuberentes setup. This will start the cloud specific controller manager in your kubernetes setup.
The downgrade steps are also the same as before for all the components except the cloud-controller-manager. In case of the cloud-controller-manager, the deployment should be deleted using The downgrade steps are also the same as before for all the components except the cloud-controller-manager. In case of the cloud-controller-manager, the deployment should be deleted using

2
contributors/design-proposals/node/kubelet-cri-logging.md
View File

@ -59,7 +59,7 @@ the format and the metadata (i.e., timestamps) of the logs. In the current
implementation, kubelet calls `docker logs` with parameters to return the log implementation, kubelet calls `docker logs` with parameters to return the log
content. As of now, docker only supports `log` operations for the “journal” and content. As of now, docker only supports `log` operations for the “journal” and
“json-file” drivers [2]. In other words, *the support of `kubectl logs` is not “json-file” drivers [2]. In other words, *the support of `kubectl logs` is not
universal in all kuernetes deployments*. universal in all kubernetes deployments*.
**Cluster logging support** **Cluster logging support**