Use cluster endpoint at startup

[piceri]

This change allows deployment tracker to use the cluster endpoint at startup to send the current state of the cluster. This will reduce the load cause at startup when deployment tracker sends the state of the cluster one container at a time.

Change details:

• While the informers sync, add events are no longer added to the work queue
• Once the informers have synced, use the pod informer to get the current list of running pods
• Any new events are then added the the work queue
• Current pod list is processed and deduped by deployment name + digest
• Send the list to the cluster endpoint
  • If this fails, deployment tracker does not continue to run
• Use the response to fill observed and unknown caches

[ajbeattie]

Nice 💯, looking great on initial pass. Still working through some of the changes but wanted to go ahead and raise the Job/CronJob suggestion ⬇️

[Copilot]

Pull request overview

This PR adds a startup “cluster sync” path so deployment-tracker can post the current cluster state in a single request to the deployment-record cluster endpoint, reducing startup load versus posting one container at a time.

Changes:

• Introduces new deployment record data models to support the cluster endpoint request/response payloads.
• Adds PostCluster (and refactors PostOne to share retry logic) in the deployment record client, with accompanying unit tests.
• Updates the controller startup flow to (a) suppress enqueueing during informer sync, (b) list current pods, (c) post cluster state, then (d) seed observed/unknown caches before starting workers.

Show a summary per file

File	Description
pkg/deploymentrecord/record.go	Refactors record types into base/request/response structs for cluster endpoint support.
pkg/deploymentrecord/client.go	Adds cluster endpoint posting and shared retry helper; updates request body builders.
pkg/deploymentrecord/client_test.go	Adds PostCluster and URL-escaping tests; updates record test helpers.
internal/controller/reporting.go	Implements building sync records, posting cluster sync, and filling caches; refactors record building.
internal/controller/reporting_test.go	Adds tests for sync processing, dedupe, and cache fill behavior; updates poster call assertions.
internal/controller/controller.go	Adds startup sync gating via atomic.Bool and calls sync processing after informer sync.
internal/controller/controller_test.go	Extends mock poster to support PostCluster; adds mock metadata aggregator for new code paths.
internal/controller/controller_integration_test.go	Updates integration test mocks/types for renamed record type and new interface method.

Copilot's findings

Tip

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

• Files reviewed: 8/8 changed files
• Comments generated: 4

[ajbeattie]

Some notes on the changes to this PR to use the async cluster job endpoint (rather than the synchronous set cluster endpoint):

• As noted in the config comment, the new behavior is off by default as it requires us to enable the endpoint on the backend
• I primarily tested the new functionality with a local mock server that has richer responses in order to simulate various job endpoint responses.

[Copilot]

Copilot's findings

• Files reviewed: 10/10 changed files
• Comments generated: 5