Our project recently migrated away from Stackdriver Logging. However, I cannot figure out how to get rid of the fluentd-cloud-logging-* pods in the kube-system namespace. If I delete the individual pods, they come right back.
How do I kill them off for good?
It's not clear to me how they're getting recreated; there is certainly no DaemonSet bringing them back.
I already set monitoringService to none in the configuration described by gcloud container clusters describe.
The fluentd-cloud-logging pods in the kube-system namespace are defined in the /etc/kubernetes/manifests/ folder of each host machine; that is, they're defined using the Static Pods mechanism.
As of this time, there's no way to change the setting globally. As a workaround, though, I can just delete the file in the manifests folder on each node, using something like the startup script pod. When the file is deleted, the pod will be deleted as well.
(Thanks to GCP support for this answer.)
来源：https://stackoverflow.com/questions/42380626/how-do-i-disable-the-stackdriver-logging-agent-in-a-cluster