Epic Goal

As an administrator of the GitOps Operator, I want to control how images are pulled for Argo CD components. This configuration should be possible at two levels:

• Operator level (via Subscription or global setting) to define defaults for all Argo CD instances.

• Individual Argo CD instance level (via the ArgoCD Custom Resource) to override and fine-tune policies per deployment.

Why is this important?

Currently, the OpenShift GitOps components default to imagePullPolicy: Always. This causes images to be re-pulled every time pods are restarted, such as during node maintenance or scaling events. While this ensures the latest image for mutable tags, it creates unnecessary network overhead in production environments where immutable images are used.

By providing administrators with the ability to configure image pull policies, we can:

• Reduce unnecessary network load during cluster maintenance.

• Improve Pod startup times by leveraging cached images.

• Allow flexibility for development (where Always may still be useful) vs. production (where IfNotPresent or digest pinning is preferred).

Scenarios

1. ...

Other Considerations

• <Call out anything explicitly as Out of Scope?>
• <Call out internal and external dependencies?>
• <Are there any known previous works?>
• <Any unanswered questions?>

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.