如何禁用群集中的Stackdriver Logging代理?

本文介绍了如何禁用群集中的Stackdriver Logging代理?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我们的项目最近从Stackdriver Logging迁移了.但是，我无法弄清楚如何摆脱kube-system名称空间中的fluentd-cloud-logging-* pod.如果我删除单个吊舱，它们会马上回来.

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.

我如何彻底杀死他们?

我不清楚它们是如何重新创建的；当然，没有DaemonSet将它们带回.

It's not clear to me how they're getting recreated; there is certainly no DaemonSet bringing them back.

我已经按照gcloud container clusters describe所述的配置将monitoringService设置为none.

I already set monitoringService to none in the configuration described by gcloud container clusters describe.

推荐答案

在每台主机的/etc/kubernetes/manifests/文件夹中定义了kube-system命名空间中的流畅的云记录pod.也就是说，它们是使用静态容器机制定义的.

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.

(感谢GCP支持此答案.)

(Thanks to GCP support for this answer.)