Story (Required)

Health index for 1.7.3 and [1.6.6|https://catalog.redhat.com/software/containers/openshift-gitops-1/argocd-rhel8/604287a75a00810ecaf7bcf0?architecture=amd64&tag=v1.6.6-1&push_date=1679597203000&container-tabs=security] has been dropped to grade B. We need another patch release for 1.6 and 1.7.

For example, Argo CD container status for release 1.7.3 can be verified using
https://catalog.redhat.com/software/containers/openshift-gitops-1/argocd-rhel8/604287a75a00810ecaf7bcf0?tag=v1.7.3-4&push_date=1679598670000&container-tabs=security

Background (Required)

NA

Out of scope

Any changes to the source code.

Approach (Required)

Since we don't have the Botas and release-driver in place. The process has to be taken care manually.

The process is same as the any z-stream release.

Dependencies

NA

Acceptance Criteria (Mandatory)

• Update the Midstream Product version to 1.7.4 and 1.6.7
• No changes made to the upstream_sources.yaml
• Trigger check-patch (which will fail for the first time of every new release)
• Merge the patch forcefully
• Trigger build-pipleine
• Wait for the IIB. Share the IIB details with the QE team
• Create Erratas
• Get the required approvals on the erratas
• Update the builds in the erratas
• Co-ordinate the release

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