-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.16.0
-
Quality / Stability / Reliability
-
False
-
-
1
-
None
-
No
-
-
None
-
None
-
None
-
T&PS 2024 #4, T&PS 2024 #5
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Looking at the doc
We see this example with extraManifests:
apiVersion: lca.openshift.io/v1alpha1
kind: ImageBasedUpgrade
metadata:
name: example-upgrade
spec:
stage: Idle
seedImageRef:
version: <target_version>
image: <seed_container_image>
pullSecretRef: <seed_pull_secret>
additionalImages:
name: ""
namespace: ""
autoRollbackOnFailure: {}
# disabledForPostRebootConfig: "true"
# disabledForUpgradeCompletion: "true"
# disabledInitMonitor: "true"
# initMonitorTimeoutSeconds: 1800
# extraManifests:
# - name: sno-extra-manifests
# namespace: openshift-lifecycle-agent
oadpContent:
- name: oadp-cm-example
namespace: openshift-adp
extraManifest has number 8 assigned to it with the following explanation following
(Optional) Specify the list of ConfigMap resources that contain the additional extra manifests that you want to apply to the target cluster. You can also add your custom catalog sources that you want to retain after the upgrade.
The doc is missing an example of such a configmap