We recently updated to CABPT & CACPPT to the latest version in order to support Talos 1.6 and appear to have faced a regression around logging.
Versions / Environment
Kubernetes: 1.27.5
Talos: Current 1.5.5 (vSphere OVA) => Target 1.6.1
Cluster API Operator: 0.7.0
Cluster API Core: 1.6.0
Cluster API Infrastructure: vSphere 1.8.4
Cluster API Bootstrap: Talos 0.6.3 (updated from 0.6.2)
Cluster API CP: Talos 0.5.4 (updated from 0.5.3)
VMWare ESXi: 7.0.3
Description
Since the update of CABPT from 0.6.2 to 0.6.3 & CACPPT from 0.5.3 to 0.5.4, we faced a regression in logs with startup errors. Note that those errors are non-blocking and the operator is still processing the underlying CRs; however, we are completely blind from a logging perspective.
Greetings,
We recently updated to CABPT & CACPPT to the latest version in order to support Talos 1.6 and appear to have faced a regression around logging.
Versions / Environment
Description
Since the update of CABPT from 0.6.2 to 0.6.3 & CACPPT from 0.5.3 to 0.5.4, we faced a regression in logs with startup errors. Note that those errors are non-blocking and the operator is still processing the underlying CRs; however, we are completely blind from a logging perspective.
CABPT Logs using version 0.6.3:
CACPPT Logs using version 0.5.4:
Logs were fully operational using the previous patch version:
CACPPT Logs using version 0.5.3:
Reproduces Steps
The issue can be easily reproduced via the following steps:
Apply basic CAPI manifests
Check logs