19bf9d0624
Only run the systemd-journal plugin when on a platform that requests it. The plugin crashes the fluentd process if the journal isn't present, so it can't just be run blindly in all configurations.
54 lines
1.6 KiB
YAML
54 lines
1.6 KiB
YAML
# This config should be kept as similar as possible to the one at
|
|
# cluster/saltbase/salt/fluentd-gcp/fluentd-gcp.yaml
|
|
apiVersion: v1
|
|
kind: Pod
|
|
metadata:
|
|
name: fluentd-cloud-logging
|
|
namespace: kube-system
|
|
labels:
|
|
k8s-app: fluentd-logging
|
|
spec:
|
|
dnsPolicy: Default
|
|
containers:
|
|
- name: fluentd-cloud-logging
|
|
image: gcr.io/google_containers/fluentd-gcp:1.21
|
|
command:
|
|
- '/bin/sh'
|
|
- '-c'
|
|
# This is pretty hacky, but ruby relies on libsystemd's native code, and
|
|
# the ubuntu:16.04 libsystemd doesn't play nice with the journal on GCI
|
|
# hosts. Work around the problem by copying in the host's libsystemd.
|
|
- 'rm /lib/x86_64-linux-gnu/libsystemd* && cp /host/lib/libsystemd* /lib/x86_64-linux-gnu/ && /usr/sbin/google-fluentd -q -c /etc/google-fluentd/google-fluentd-journal.conf'
|
|
resources:
|
|
limits:
|
|
memory: 200Mi
|
|
requests:
|
|
# Any change here should be accompanied by a proportional change in CPU
|
|
# requests of other per-node add-ons (e.g. kube-proxy).
|
|
cpu: 80m
|
|
memory: 200Mi
|
|
volumeMounts:
|
|
- name: varlog
|
|
mountPath: /var/log
|
|
- name: varlibdockercontainers
|
|
mountPath: /var/lib/docker/containers
|
|
readOnly: true
|
|
- name: journaldir
|
|
mountPath: /var/log/journal
|
|
- name: libsystemddir
|
|
mountPath: /host/lib
|
|
terminationGracePeriodSeconds: 30
|
|
volumes:
|
|
- name: varlog
|
|
hostPath:
|
|
path: /var/log
|
|
- name: varlibdockercontainers
|
|
hostPath:
|
|
path: /var/lib/docker/containers
|
|
- name: journaldir
|
|
hostPath:
|
|
path: /var/log/journal
|
|
- name: libsystemddir
|
|
hostPath:
|
|
path: /usr/lib64
|