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

Image Updater: Release notes documentation for tech preview

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      Argo CD Image Updater is now available as a Technology Preview feature in Red Hat OpenShift GitOps. Argo CD Image Updater is a tool that automatically updates container images of Kubernetes workloads managed by Argo CD. It tracks image versions in applications, as specified by ImageUpdater Custom Resources (CR), and automatically updates them by setting parameter overrides via Argo CD API or git write-back method. The image updater supports applications built with Kustomize or Helm. For more information, see Overview of the [Argo CD Image Updater](https://argocd-image-updater.readthedocs.io/).

      !! Important

      The GitOps Argo CD Image Updater feature is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

      For more information about the support scope of Red Hat Technology Preview features, see [Technology Preview Features Support Scope](https://access.redhat.com/support/offerings/techpreview/).

      [GITOPS-7610](https://issues.redhat.com/browse/GITOPS-7610)
      Show
      Argo CD Image Updater is now available as a Technology Preview feature in Red Hat OpenShift GitOps. Argo CD Image Updater is a tool that automatically updates container images of Kubernetes workloads managed by Argo CD. It tracks image versions in applications, as specified by ImageUpdater Custom Resources (CR), and automatically updates them by setting parameter overrides via Argo CD API or git write-back method. The image updater supports applications built with Kustomize or Helm. For more information, see Overview of the [Argo CD Image Updater]( https://argocd-image-updater.readthedocs.io/ ). !! Important The GitOps Argo CD Image Updater feature is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see [Technology Preview Features Support Scope]( https://access.redhat.com/support/offerings/techpreview/ ). [ GITOPS-7610 ]( https://issues.redhat.com/browse/GITOPS-7610 )
    • Technology Preview
    • Proposed
    • GitOps Tangerine Sprint 22

      Story (Required)

      • In order to include Image Updater as Tech Preview in upcoming GitOps release, engineering will need to provide release notes content.

      Background and Approach (Required)

      Out of Scope

      • This story covers only release notes content, and the product documentation for image updater will be addressed separately.

      Dependencies

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

      Acceptance Criteria (Mandatory)

      • <Describe edge cases to consider when implementing the story and defining tests.>
      • <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story.>

      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.

              cfang@redhat.com Cheng Fang
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: