kubernetes/cluster/addons/fluentd-elasticsearch/fluentd-es-image
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
..
clean-apt Base Fluentd image off debian:stretch-slim for systemd with LZ4 2017-08-15 15:55:13 +02:00
clean-install Base Fluentd image off debian:stretch-slim for systemd with LZ4 2017-08-15 15:55:13 +02:00
Dockerfile updated fluentd-es-image to use fluentd 1.1.0 2018-01-19 17:20:30 +01:00
fluent.conf updated fluentd-es-image to use fluentd 1.1.0 2018-01-19 17:20:30 +01:00
Gemfile switch to new detect-exeptiions plugin release 0.0.9 2018-01-20 01:34:46 +01:00
Makefile Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
README.md Switch to k8s.gcr.io vanity domain 2018-02-07 21:14:19 -08:00
run.sh Base Fluentd image off debian:stretch-slim for systemd with LZ4 2017-08-15 15:55:13 +02:00

Collecting Docker Log Files with Fluentd and Elasticsearch

This directory contains the source files needed to make a Docker image that collects Docker container log files using Fluentd and sends them to an instance of Elasticsearch. This image is designed to be used as part of the Kubernetes cluster bring up process. The image resides at GCR under the name k8s.gcr.io/fluentd-elasticsearch.

Analytics