You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/drafts/upgrade-support.md
+8-8
Original file line number
Diff line number
Diff line change
@@ -42,17 +42,17 @@ spec:
42
42
packageName: <package_name>
43
43
serviceAccount:
44
44
name: <service_account>
45
-
upgradeConstraintPolicy: Ignore
45
+
upgradeConstraintPolicy: SelfCertified
46
46
version: "<version_or_version_range>"
47
47
```
48
48
49
49
where setting the `upgradeConstraintPolicy` to:
50
50
51
-
`Ignore`
51
+
`SelfCertified`
52
52
: Does not limit the next version to the set of successors, and instead allows for any downgrade, sidegrade, or upgrade.
53
53
54
-
`Enforce`
55
-
: Only allows the next version to come from the successors list. This is the default value. If the `upgradeConstraintPolicy` parameter is not defined in an extension's CR, then the policy is set to `Enforce` by default.
54
+
`CatalogProvided`
55
+
: Only allows the next version to come from the successors list. This is the default value. If the `upgradeConstraintPolicy` parameter is not defined in an extension's CR, then the policy is set to `CatalogProvided` by default.
56
56
57
57
## Upgrades
58
58
@@ -74,11 +74,11 @@ You must verify and perform upgrades manually in cases where automatic upgrades
74
74
75
75
**Warning:** If you want to force an upgrade manually, you must thoroughly verify the outcome before applying any changes to production workloads. Failure to test and verify the upgrade might lead to catastrophic consequences such as data loss.
76
76
77
-
As a package admin, if you must upgrade or downgrade to version that might be incompatible with the currently installed version, you can set the `.spec.upgradeConstraintPolicy` field to `Ignore` on the relevant `ClusterExtension` resource.
77
+
As a package admin, if you must upgrade or downgrade to version that might be incompatible with the currently installed version, you can set the `.spec.upgradeConstraintPolicy` field to `SelfCertified` on the relevant `ClusterExtension` resource.
78
78
79
-
If you set the field to `Ignore`, no upgrade constraints are set on the package. As a result, you can change the version to any version available in the catalogs for a given package.
79
+
If you set the field to `SelfCertified`, no upgrade constraints are set on the package. As a result, you can change the version to any version available in the catalogs for a given package.
80
80
81
-
Example `ClusterExtension` with `.spec.upgradeConstraintPolicy` field set to `Ignore`:
81
+
Example `ClusterExtension` with `.spec.upgradeConstraintPolicy` field set to `SelfCertified`:
0 commit comments