You can run your own but you need to maintain it on your end to make sure everything works. Do not try to make modifications to the existing daemonset because they will be overwritten because of the annotation
addonmanager.kubernetes.io/mode: Reconcile on the daemonset. You can follow the documentation to disable stackdriver gcloud beta container clusters update --logging-service=none CLUSTER punit agrawal dev-ops lead new product development ebay From: <kubernetes-users@googlegroups.com> on behalf of Yifeng Huang <fr...@rideos.ai> Reply-To: "kubernetes-users@googlegroups.com" <kubernetes-users@googlegroups.com> Date: Wednesday, August 29, 2018 at 4:19 PM To: Kubernetes user discussion and Q&A <kubernetes-users@googlegroups.com> Subject: [kubernetes-users] How to upgrade managed fluentd on GKE? Hello, We have a quick question about the managed fluentd that is installed on GKE clusters with logging enabled. This particular cluster was created a few months ago. The installed fluentd DaemonSet appears to use a stackdriver-logging-agent image from around April: gcr.io/stackdriver-agents/stackdriver-logging-agent:0.2-1.5.30-1-k8s (April 4) However, on GCR there are a number of images that are newer than this one. The latest is 0.4-1.5.35-1-k8s from Aug 16. The fluentd DaemonSet in our cluster does not appear to have been modified or updated since the cluster was created. Our question is whether it is possible to upgrade the fluentd DaemonSet to use a newer image tag, and how to do so. The documentation here<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkubernetes.io%2Fdocs%2Ftasks%2Fdebug-application-cluster%2Flogging-stackdriver%2F%23configuring-stackdriver-logging-agents&data=02%7C01%7Cpunagrawal%40ebay.com%7C6dcfab1191fd407e26a708d60e05db57%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636711815648517701&sdata=jTFA6Qb5rTsTb%2Bzm%2Bei1AqTAmaNLwUpsesgREyRZEag%3D&reserved=0> suggests that we can't manually modify the DaemonSet through kubectl (it's "managed and supported through GKE") -- if so, we are somewhat surprised that the fluentd DaemonSet hasn't been upgraded without our intervention. For context: the reason we are interested in upgrading fluentd is that we are experiencing segfaults in the fluent-plugin-google-cloud when exporting to Stackdriver. We noticed several somewhat-related issues being fixed in ruby-grpc and ruby-protobuf in the meantime, so we would like to try out a newer fluentd image to see if that resolves the issue. Thanks for your help! - Yifeng -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com<mailto:kubernetes-users+unsubscr...@googlegroups.com>. To post to this group, send email to kubernetes-users@googlegroups.com<mailto:kubernetes-users@googlegroups.com>. Visit this group at https://groups.google.com/group/kubernetes-users<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fgroup%2Fkubernetes-users&data=02%7C01%7Cpunagrawal%40ebay.com%7C6dcfab1191fd407e26a708d60e05db57%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636711815648517701&sdata=XGgeqQ3qzoorh4y3FBbZzcRv0oUjtxj1Jha22ac3Gi4%3D&reserved=0>. For more options, visit https://groups.google.com/d/optout<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7Cpunagrawal%40ebay.com%7C6dcfab1191fd407e26a708d60e05db57%7C46326bff992841a0baca17c16c94ea99%7C0%7C0%7C636711815648527706&sdata=d7TWK%2FcrFgabtekqrVZp%2Bxl2aw0TCZWzlm0mmhvnjVg%3D&reserved=0>. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
