You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because certain controllers (e.g. status aggregation controller) run by the FTC controller wait for cache sync in the main thread, a wrongly configured FTC can prevent the whole FTC controller from progressing.
The image above shows the logs from the FTC controller indicating that it got blocked after starting the status controller.
Steps to reproduce:
Run the KubeAdmiral controller manager against a 1.23 Kubernetes host cluster using the default FTCs in config/sample/host/01-ftc.yaml.
Because the yaml file contains an older version of CronJob, informers for CronJob will fail to list and their informer cache will never be synced, resulting in the above behavior
The text was updated successfully, but these errors were encountered:
Because certain controllers (e.g. status aggregation controller) run by the FTC controller wait for cache sync in the main thread, a wrongly configured FTC can prevent the whole FTC controller from progressing.
The image above shows the logs from the FTC controller indicating that it got blocked after starting the status controller.
Steps to reproduce:
config/sample/host/01-ftc.yaml
.The text was updated successfully, but these errors were encountered: