cloud-native-toolkit / cloud-native-toolkit/multi-tenancy-gitops
Update CP4D CatalogSources to pinned versions
Open
- Dominant language
- Shell
- Stars
- 120
- Forks
- 713
- PR merge metrics
- No merged PRs in 30d
Description
Instead of using the generic IBM CatalogSource, use the version specific CatalogSource to control the version of the Cloud Pak. This will grant users with more control on when a version of a CP will be upgraded otherwise, if the Operator is set to update automatically, the latest release in a `Channel` version will be applied as soon as its released.
@atbijo, let's have a look at this.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.