Description of problem:
oc-mirror produces images signature config maps in JSON format, inconsistent with other manifests which are normally in YAML. That breaks some automation, especially Multicloud Operators Subscription controller which expects manifests in YAML only.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Perform release payload mirroring as documented
2. Check 'release-signatures' directory
Actual results:
There is a mix of YAML and JSON files with kubernetes manifests.
Expected results:
Manifests are stored in one format, either YAML or JSON
Additional info:
- is related to
-
CLID-150 As a customer I want to be sure the release signatures are made available
-
- Testing
-
-
OCPBUGS-38343 Should save the release signature in the archive tar file instead of count on the enterprise cache (or working-dir)
-
- Verified
-
- links to
-
RHEA-2024:6122
OpenShift Container Platform 4.18.z bug fix update
