mkdir ~/environment/fluentd cd ~/environment/fluentd wget https://eksworkshop.com/logging/deploy.files/fluentd.yml
Explore the fluentd.yml to see what is being deployed. There is a link at the bottom of this page. The Fluentd log agent configuration is located in the Kubernetes ConfigMap. Fluentd will be deployed as a DaemonSet, i.e. one pod per worker node. In our case, a 3 node cluster is used and so 3 pods will be shown in the output when we deploy.
Update REGION and CLUSTER_NAME environment variables in fluentd.yml to the ones for your values. Currently, they are set to us-west-2 and eksworkshop-eksctl by default. Adjust this change in the ‘env’ section of the fluentd.yml file:
env: - name: REGION value: us-west-2 - name: CLUSTER_NAME value: eksworkshop-eksctl
sed -e "s/us-west-2/$AWS_REGION/" -i ~/environment/fluentd/fluentd.yml kubectl apply -f ~/environment/fluentd/fluentd.yml
Watch for all of the pods to change to running status
kubectl get pods -w --namespace=kube-system
We are now ready to check that logs are arriving in CloudWatch Logs
Select the region that is mentioned in fluentd.yml to browse the Cloudwatch Log Group if required.