History

Tim Hockin 3586986416 Switch to k8s.gcr.io vanity domain This is the 2nd attempt. The previous was reverted while we figured out the regional mirrors (oops). New plan: k8s.gcr.io is a read-only facade that auto-detects your source region (us, eu, or asia for now) and pulls from the closest. To publish an image, push k8s-staging.gcr.io and it will be synced to the regionals automatically (similar to today). For now the staging is an alias to gcr.io/google_containers (the legacy URL). When we move off of google-owned projects (working on it), then we just do a one-time sync, and change the google-internal config, and nobody outside should notice. We can, in parallel, change the auto-sync into a manual sync - send a PR to "promote" something from staging, and a bot activates it. Nice and visible, easy to keep track of.		2018-02-07 21:14:19 -08:00
..
fluentd-gcp-image	Update docs for user-guide	2017-06-27 12:21:49 +08:00
podsecuritypolicies	Reorganize addon PodSecurityPolicies	2017-11-10 13:57:32 -08:00
OWNERS	Fix username case in OWNERS files	2017-03-07 16:45:40 -08:00
README.md	Add readme for fluentd-elasticsearch addon	2017-03-22 11:27:48 +01:00
event-exporter.yaml	Switch to k8s.gcr.io vanity domain	2018-02-07 21:14:19 -08:00
fluentd-gcp-configmap.yaml	Remove salt configuration from the fluentd-gcp configuration.	2018-01-22 21:06:09 -08:00
fluentd-gcp-ds-sa.yaml	Fix setting resources in fluentd-gcp plugin	2017-11-22 12:40:50 +01:00
fluentd-gcp-ds.yaml	Switch to k8s.gcr.io vanity domain	2018-02-07 21:14:19 -08:00

README.md

Stackdriver Logging Agent

==============

Stackdriver Logging Agent is a DaemonSet which spawns a pod on each node that reads logs, generated by kubelet, container runtime and containers and sends them to the Stackdriver. When logs are exported to the Stackdriver, they can be searched, viewed, and analyzed.

Learn more at: https://kubernetes.io/docs/tasks/debug-application-cluster/logging-stackdriver