Story (Required)

• As a user, I want to know the status of my ImageUpdater CRD at every given time. I want the status to be present in the CRD itself.

Background and Approach (Required)

• Status fields are defined in https://docs.google.com/document/d/17zLPQYsfjvl1orBrCoUBhFiRMVtIlN5dYTMmpFMQxJE/edit?usp=sharing 

Out of Scope

• <Defines what is not included in this story.>

Dependencies

• <Describes what this story depends on. Dependent stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

• The status field gets set correctly on the CRD
• Unit and e2e tests are added with all scenarios.
• PR merged to source repo
• Doc update merged

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.