Changing fluent-bit log level in a TKGi cluster

Products

• VMware Tanzu Kubernetes Grid Integrated Edition

Issue/Introduction

TKGi's Fluent-bit log_level to warn by default. This KB shows how to change fluent-bit log level.

Please note that changing to debug will generate a lot of logs, it is recommended to change the log level for troubleshooting purposes only.

Resolution

Here are the steps for changing fluent-bit log level

1. Retrieve your TKGi cluster credential

2. Create a back up of config maps before editing so you can easily revert back in case of user error

kubectl get configmaps -n pks-system -oyaml fluent-bit > fluent-bit-configmaps-backup.yaml

3. Edit config map

kubectl edit configmaps -n pks-system -oyaml fluent-bit

4. Under fluent-bit.conf look for Log_Level  and change accordingly

fluent-bit.conf:  | 
    [SERVICE]
    Flush          1
    Log_Level   warning
    Daemon
    ... 

5. After editing config map

kubectl rollout restart ds fluent-bit -n pks-system

Please note that the changes in the ConfigMap are not persistent across TKGi upgrades