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
With the addition of the CRD Upgrade Safety preflight check, our
existing example of upgrading argocd from 0.5.0 to 0.6.0 no longer
serves as a good example. This commit changes the example to use an
update from 0.2.0 to 0.2.1 which no longer fails the CRD Upgrade check,
and also doesn't violate our restriction on automatic upgrades between
minor versions with a major version of zero.
Signed-off-by: Tayler Geiger <[email protected]>
Copy file name to clipboardExpand all lines: docs/tutorials/upgrade-extension.md
+22-34Lines changed: 22 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,16 +11,17 @@ For information on downgrading an extension, see [Downgrade an Extension](downgr
11
11
12
12
## Prerequisites
13
13
14
-
* You have an extension installed
14
+
* You have a ClusterExtension installed
15
15
* The target version is compatible with OLM v1 (see [OLM v1 limitations](../project/olmv1_limitations.md))
16
-
* CRD compatibility between the versions being upgraded or downgraded (see [CRD upgrade safety](../concepts/crd-upgrade-safety.md))
17
-
* The installer service account's RBAC permissions are adequate for the target version (see [Minimal RBAC for Installer Service Account](../howto/derive-service-account.md))
16
+
* Any changes to the CustomResourceDefinition in the new version meet compatibility requirements (see [CRD upgrade safety](../concepts/crd-upgrade-safety.md))
17
+
* The installer ServiceAccount's RBAC permissions are adequate for the target version (see [Minimal RBAC for Installer Service Account](../howto/derive-service-account.md))
18
+
* You are not attempting to upgrade between minor versions with a major version of zero (see [Upgrades within the major version zero](../concepts/upgrade-support.md#upgrades-within-the-major-version-zero))
18
19
19
20
For more detailed information see [Upgrade Support](../concepts/upgrade-support.md).
20
21
21
22
## Procedure
22
23
23
-
Suppose we have successfully created and installed v0.5.0 of the ArgoCD operator with the following `ClusterExtension`:
24
+
Suppose we have successfully created and installed v0.2.0 of the ArgoCD operator with the following `ClusterExtension`:
24
25
25
26
```yaml title="Example CR"
26
27
apiVersion: olm.operatorframework.io/v1
@@ -35,7 +36,7 @@ spec:
35
36
sourceType: Catalog
36
37
catalog:
37
38
packageName: argocd-operator
38
-
version: 0.5.0
39
+
version: 0.2.0
39
40
```
40
41
41
42
* Update the version field in the ClusterExtension resource:
@@ -54,7 +55,7 @@ spec:
54
55
sourceType: Catalog
55
56
catalog:
56
57
packageName: argocd-operator
57
-
version: 0.6.0# Update to version 0.6.0
58
+
version: 0.2.1# Update to version 0.2.1
58
59
EOF
59
60
```
60
61
@@ -66,27 +67,14 @@ spec:
66
67
Alternatively, you can use `kubectl patch` to update the version field:
0 commit comments