Epic Goal

• Officially mark Nutanix S3 storage as a supported backend for the OpenShift integrated registry

Why is this important?

• Customers using Nutanix S3 backend want an officially supported OCP deployment
• We believe there is no technical hurdle to support this and no code changes needed but formal validation needs to happen via QE

Scenarios

1. In a day 2 configuration, the customer can leverage the integrated registry operator to configure a Nutanix S3 bucket as the backend for the image blob store

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Documentation is provided in the Image Registry operator configuration section, e.g. https://docs.openshift.com/container-platform/4.12/registry/configuring_registry_storage/configuring-registry-storage-aws-user-infrastructure.html

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>