Hello-

I have a kops-managed cluster running in AWS, wherein many of my nodes
continue to bounce between Ready <--> NotReady. I'm trying to deploy
fluent-bit as a DaemonSet to each node to capture all the systemd
journal docker and kubelet service logs in a centralized fashion using
the fluent-bit 'systemd' input plugin. Attached is the relevant
ConfigMap I'm using, in conjunction with the deployment files available
in the following repository.

https://github.com/fluent/fluent-bit-kubernetes-logging

When the DaemonSet is deployed with the attached ConfigMap in my AWS
cluster, I get no kubelet logs written to STDOUT, though I can verify
that kubelet logs are being generated by looking at journal logs for the
kubelet service on one or more of my nodes.

As an aside, deploying the minikube-specific DaemonSet with the attached
ConfigMap in my local minikube cluster *does* result in the Docker
journal logs being written to STDOUT. It's expected that no kubelet logs
would be captured since the kubelet doesn't run as a systemd service in
the minikube VM.

Any ideas what I'm doing wrong in my AWS cluster? Alternatively, does
anyone have suggestions on a different way to centralize the kubelet
logs for all my AWS cluster nodes?

Please advise.

-V/R, Bryan

-- 
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.
apiVersion: v1
kind: ConfigMap
metadata:
  name: fluent-bit-config
  namespace: logging
  labels:
    k8s-app: fluent-bit
data:
  fluent-bit.conf: |
    [SERVICE]
        Flush         1
        Log_Level     debug
        Daemon        off

    @INCLUDE input-systemd.conf
    # @INCLUDE output-elasticsearch.conf
    @INCLUDE output-stdout.conf

  input-systemd.conf: |
    [INPUT]
        Name              systemd
        Tag               host.*
        Systemd_Filter    _SYSTEMD_UNIT=docker.service
        Systemd_Filter    _SYSTEMD_UNIT=kubelet.service

  output-elasticsearch.conf: |
    [OUTPUT]
        Name            es
        Match           *
        Host            ${FLUENT_ELASTICSEARCH_HOST}
        Port            ${FLUENT_ELASTICSEARCH_PORT}
        Logstash_Format On
        Retry_Limit     False

  output-stdout.conf: |
    [OUTPUT]
        Name            stdout
        Match           *

Reply via email to