TKGI observability-manager Pod deletes fluent-bit ClusterRole and ClusterroleBinding

Products

• VMware Tanzu Kubernetes Grid Integrated Edition

Issue/Introduction

TKGi cluster with fluent-bit installed using helm chart

On restart of observability-manager pod, it will delete the fluent-bit ClusterRole and ClusterRoleBinding

Environment

TKGi 1.21, 1.22, 1.23

Cause

The observability-manager pod identifies that "Log Sink resources" has not been enabled in TKGi Tile and deletes the ClusterRole and ClusterRoleBinding with the same name, fluent-bit.

Resolution

This is a known issue in TKGi 1.21, 1.22 and 1.23 and will be resolved in a future release.

To workaround the issue, recreate the fluent-bit clusterRole and ClusterRoleBinding.

 

Alternatively, change the value of fullnameOverride in values.yaml for the helm chart and re-install fluent-bit. The ClusterRole and ClusterRoleBinding will not be deleted once the fullnameOverride has been changed.