-
Bug
-
Resolution: Done
-
Undefined
-
4.15.0
-
Moderate
-
No
-
2
-
T&PS 2024 #5, T&PS 2024 #6
-
2
-
False
-
-
Description of problem:
By default, upgrading a cluster that has custom catalogsources defined results in the custom catalogsources disappearing after the upgrade is complete. In order to retain the user-defined catalogsources, the user must supply them through extraManifests field. This step should be added to the official documentation.
Version-Release number of selected component (if applicable):
4.15.0
How reproducible:
100%
Steps to Reproduce:
1. Upgrade a cluster with a user-defined catalogsource without adding it to extraManifests
Actual results:
The catalogsource no longer exists on the upgraded cluster
Expected results:
Doc needed to explain that this step is required to keep custom catalogsources
Additional info: