Add informer sync timeout

[piceri]

This changes adds a timeout to the informer sync process in the controller. Without this timeout, the controller can become stuck waiting for informers to sync.

For example, informers cannot sync if deployment tracker does not have the proper Kubernetes permissions but a lack of permissions does not trigger any fatal errors. This would result in the controller being stuck waiting for the sync to complete.

[Copilot]

Pull request overview

Adds a bounded timeout to the controller’s informer cache sync phase so the controller can fail fast instead of hanging indefinitely when informers can’t sync (e.g., due to missing RBAC permissions).

Changes:

• Introduces a default informer sync timeout (60s) and wires it into Controller.Run() via a timeout-derived context.
• Improves the cache-sync failure error message to hint at likely RBAC causes.
• Adds a unit test intended to verify Run() returns when informer cache sync is blocked.

Show a summary per file

File	Description
internal/controller/controller.go	Adds a controller-level informer sync timeout and uses it to bound WaitForCacheSync.
internal/controller/controller_test.go	Adds a test that simulates blocked informer listing to ensure sync timeout triggers.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 3