Skip to content

Update CP4D CatalogSources to pinned versions #240

@hollisc

Description

@hollisc

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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions