Description of problem:
The generateCatalogSource function does not generate an update strategy. This will be a problem when a targetTag is used for the catalog reference since there will be no way for the catalog to be automatically refreshed once oc mirror pushes a new catalog.
Below I've included an example CatalogSource purely for reference so you can see the update strategy portion of the YAML. For more information on this feature see Explanation of spec.updateStrategy and openshift docs for Catalog source. I'd recommend a hard coded default of {{30m0s}.
apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: my_example namespace: openshift-marketplace spec: displayName: example publisher: IBM image: icr.io/cpopen/ibm-cpd-platform-operator-catalog:v1.0 sourceType: grpc updateStrategy: # <-- this is not included registryPoll: interval: 30m0s
Version-Release number of selected component (if applicable):
4.13
How reproducible:
always
Steps to Reproduce:
1. execute oc mirror and examine the catalog source that is generated
1. execute oc mirror and examine the catalog source that is generated
Actual results:
A catalog source that does not contain {{spec.updateStrategy}}
A catalog source that does not contain {{spec.updateStrategy}}
Expected results:
A catalog source that does contain {{spec.updateStrategy}}
A catalog source that does contain {{spec.updateStrategy}}
Additional info:
none
- duplicates
-
CFE-801 Create polling CatalogSource
- Closed
- is related to
-
CLID-10 As a user I want to be able to use oc-mirror in both partial and fully disconnected install scenarios so that I can generate relevant metadata useful for validation and implementation for catalog images according to the requirements for enclave support
- Closed