github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-27 13:37:30 +00:00
Code Issues Projects Releases Wiki Activity

Review #1

Browse Source
This commit is contained in:
Daniel Kłobuszewski 2018-02-22 09:59:16 +01:00
parent 6ef5d17701
commit aac6e3f739
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
cluster/addons/fluentd-gcp/README.md
View File

@ -11,18 +11,22 @@ Learn more at: https://kubernetes.io/docs/tasks/debug-application-cluster/loggin
## Troubleshooting ## Troubleshooting
In Kubernetes clusters in version 1.10.0 or later, fluentd-gcp DaemonSet can be In Kubernetes clusters in version 1.10.0 or later, fluentd-gcp DaemonSet can be
manually scaled. This is useful e.g. when the applications running in the manually scaled. This is useful e.g. when applications running in the cluster
cluster are sending a large volume of logs (i.e. over 100kB/s), causing are sending a large volume of logs (i.e. over 100kB/s), causing fluentd-gcp to
fluentd-gcp to fail with OOM errors. Conversely, if the applications aren't fail with OutOfMemory errors. Conversely, if the applications aren't generating
generating a lot of logs, it may be useful to reduce the amount of resources a lot of logs, it may be useful to reduce the amount of resources consumed by
consumed by fluentd-gcp, making them available to other applications. To learn fluentd-gcp, making these resources available to other applications. To learn
more about Kubernetes resource requests and limits, see the official more about Kubernetes resource requests and limits, see the official
documentation ([CPU][cpu], [memory][memory]). The amount of resources requested documentation ([CPU][cpu], [memory][memory]). The amount of resources requested
by fluentd-gcp on every node in the cluster can be fetched by running following by fluentd-gcp on every node in the cluster can be fetched by running following
command: command:
``` ```
$ kubectl get ds -n kube-system -l k8s-app=fluentd-gcp -o custom-columns=NAME:.metadata.name,CPU_REQUEST:.spec.template.spec.containers[].resources.requests.cpu,MEMORY_REQUEST:.spec.template.spec.containers[].resources.requests.memory,MEMORY_LIMIT:.spec.template.spec.containers[].resources.limits.memory $ kubectl get ds -n kube-system -l k8s-app=fluentd-gcp \
-o custom-columns=NAME:.metadata.name,\
CPU_REQUEST:.spec.template.spec.containers[].resources.requests.cpu,\
MEMORY_REQUEST:.spec.template.spec.containers[].resources.requests.memory,\
MEMORY_LIMIT:.spec.template.spec.containers[].resources.limits.memory
``` ```
This will display an output similar to the following: This will display an output similar to the following: