Skip to content

Conversation

@Amr-Shams
Copy link

@Amr-Shams Amr-Shams commented Dec 29, 2025

Description

  • Fixes [Bug]: Flaky MeshSync Test due to Race Condition/Stale Data #692 : updates meshsync_controller_test.go to use direct API hits with retries (Eventually), effectively bypassing local cache staleness/race
    conditions during high-concurrency test runs.
  • Refactor: Standardizes Broker and MeshSync packages to use the controller-runtime client interface instead of Clientset.
    This PR fixes #

Notes for Reviewers
this fix introduced the way to use the client local cache as the first layer (the watcher updates the local cache through events)
during the test we needed to hit the row api for k8s for the high freq(other wise i think the cache should be more safe) wq

Signed commits

  • Yes, I signed my commits.

…tset

Update Broker and MeshSync controllers and associated packages to use the controller-runtime client for resource health checks and endpoint retrieval.

Signed-off-by: Amr-Shams <[email protected]>
Wrap the MeshSync update logic in an Eventually block to handle potential conflicts during reconciliation in test environments.

Signed-off-by: Amr-Shams <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Flaky MeshSync Test due to Race Condition/Stale Data

1 participant