Story (Required)

• See https://github.com/argoproj-labs/argocd-agent/issues/418 issue for details.

Background and Approach (Required)

• ApplicationsCount, APIsCount, ResourcesCount are stored in Redis cache and regularly updated by GitOps Engine.
• A go-routine will make a call in a regular interval
• Called function will fetch this info from cache.
• Then an event will be sent to principal with updated info
• Principal will receive event and get the info
• Principal will update this info in its Redis cache
• ArgoCD IO running on principal will pick this info from cache and show in Settings/Clusters page. 

Acceptance Criteria (Mandatory)

• Feature working as expected
• Unit and E2E test cases to test the functionality 

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.