Skip to content

Commit f3e89d1

Browse files
Update private-cloud-upgrade-guide.md
1 parent f1d731a commit f3e89d1

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

content/en/docs/deployment/private-cloud/private-cloud-upgrade-guide.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,18 +12,18 @@ This document describes how an existing installation of Mendix for Private Cloud
1212
This procedure allows you to upgrade to any supported (v1.9.0 and later) version of the Mendix for Private Cloud Operator.
1313

1414
{{% alert color="warning" %}}
15-
Read this carefully when
15+
There are special considerations that you must be aware of in the following cases:
1616

17-
* using the `mxpc-cli` installation and configuration tool version 2.20.1 or earlier;
18-
* or manually installing or upgrading CRDs with `kubectl apply`.
17+
* when using the `mxpc-cli` installation and configuration tool version 2.20.1 or earlier.
18+
* when manually installing or upgrading CRDs with `kubectl apply`.
1919

2020
Upgrading the Mendix for Private Cloud Operator in a namespace will modify global resources such as Mendix Custom Resource Definitions in the cluster.
2121

2222
[Custom Resource Definitions](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/) allow Mendix applications to be managed with Kubernetes APIs and tools such as `kubectl` and `oc`.
2323

2424
Once you have installed a particular version of the Mendix Operator into any namespace in the cluster, you should not install older versions of the Mendix Operator into the same cluster, even if they are in other namespaces. This is because all the CRDs are global resources and operators in all namespaces use the same one, which may not be compatible across versions.
2525

26-
Starting from `mxpc-cli` version 2.21.0, the installation or upgrade process will check to see if the cluster has a newer CRD version than the CRDs bundled with `mxpc-cli`. If the cluster has newer CRDs, `mxpc-cli` will skip the CRD installation step - and avoid downgrading CRDs.
26+
Starting from `mxpc-cli` version 2.21.0, the installation or upgrade process checks to see if the CRDs in the cluster are newer than the CRDs bundled with `mxpc-cli`. If the cluster has newer CRDs, `mxpc-cli` will skip the CRD installation step and avoid downgrading CRDs.
2727
{{% /alert %}}
2828

2929
If you are using your own private registry, follow the [Migrating to Your Own Registry](/developerportal/deploy/private-cloud-migrating/) guide first

0 commit comments

Comments
 (0)