-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
BU Product Work
-
3
-
False
-
None
-
False
-
OCPSTRAT-244 - Serve OpenShift release signatures via Cincinnati for restricted network
-
-
-
OTA 239, OTA 240, OTA 244
OTA-910 taught Cincinnati how to retrieve signatures from upstream stores. OTA-913 taught Cincinnati how to include signatures in graph-data tarballs. OTA-914 taught oc-mirror to include signatures in graph-data container images. This ticket is about teaching Cincinnati to consume signatures from graph-data container images, so that Cincinnati running under the OpenShift Update Service in disconnected/restricted-networks (who cannot reach upstream signature stores) can still serve the OTA-909 API to local cluster-version operators.
Definition of done:
A local OpenShift Update Service deployment in a disconnected/restricted-network can serve /api/upgrades_info/signatures/${ALGO}/${DIGEST}/signature-# for releases mirrored by oc-mirror.
- blocks
-
OTA-1047 Release OSUS v5.0.3
- Closed
-
OTA-1014 Add metadata-helper deployment to OSUS operator
- Closed
-
OTA-918 Placeholder: New OpenShift Update Service release to ship this feature
- Closed
- is blocked by
-
OTA-914 Teach oc-mirror to include signatures in graph-data images
- Closed
-
OTA-909 Define an API for Cincinnati serving signatures to the cluster-version operator
- Closed
-
OTA-911 Configure Red-Hat-hosted Cincinnati to retrieve and serve image signatures
- Closed
-
OTA-949 Finalize filesystem schema for signatures in the graph-data tarball
- Closed
- links to
-
RHEA-2024:130539 RHEA: OSUS Enhancement Update