Epic Goal

• allow for the configuration to limit image updater to manage applications in a specific namespace.

Why is this important?

• image updater currently mananges all applications across namespaces in order to support apps in any namespace feature. In a large installation with many applications, it can be resource intensive and be a performance bottleneck.
• for users not interested in apps in any namespace, there need to be a way to avoid this performance overhead by scoping image updater to one single namespace.

Scenarios

1. see image updater github issue https://github.com/argoproj-labs/argocd-image-updater/pull/1112

Other Considerations

• backward compatibility: current deployment of image updater using apps in any namespace should still be supported and not affected adversely.

Definition of Ready

• The epic has been broken down into stories.
• Stories have been scoped.
• The epic has been stack ranked.

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository / project.
• 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.
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.