Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-2427

Blog for Image updater in OpenShift GitOps

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • None
    • Documentation
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False

      Story (Required)

      As a user of OpenShift GitOps, I would like a blog that talks about how image updater can be used through OpenShift GItOps

      Background (Required)

      Standard practice involves publishing a blog for new components brought into OpenShift GItOps

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      Publish a blog bringing attention to Image Updater being available for configuration through OpenShift GitOps

      Dependencies

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

      Acceptance Criteria (Mandatory)

      Blog is published either on medium or red hat developer
      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              Unassigned Unassigned
              jrao@redhat.com Jaideep Rao
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: