Merge pull request mendix#5769 from zlogic/release-mx4pc-2.10.2

Release notes for Mx4PC version 2.10.2 (planned release date 17 March)

Author: katarzyna-koltun-mx

content/en/docs/developerportal/deploy/private-cloud/private-cloud-cluster/private-cloud-migrating.md

@@ -46,6 +46,11 @@ Follow these steps to export the Mendix components and store them on your local
 
     The components you selected will be extracted from the Mendix repository and saved on your local machine. This will be in the folder `C:\Users\<User id>\.mxpc-cli\registry-migration` on Windows or `home/<User id>/.mxpc-cli/registry-migration` for Mac and U*ix. This can take some time. Wait for the message*The images for the selected components were exported successfully in tarballs*.
 
+{{% alert color="info" %}}
+To avoid downloading too many images, there is a default limit on the number of images that will be downloaded. You can check the current limit by running the following command: `./mxpc-cli registry-migration --help`
+Since version 2.10.2 of `mxpc-cli`, you can change this limit by using a `--max-images` commandline argument, for example, `mxpc-cli registry-migration --max-images=50`.
+{{% /alert %}}
+
 ## 5 Import Mendix Components Into Your Own Registry
 
 Once you have the Mendix components saved on your local machine, you can import them into your own registry. This means that, once configured, Mendix will be able to find them, even if you have an air-gapped installation which is not connected to the internet.

content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md

@@ -13,6 +13,18 @@ For information on the current status of deployment to Mendix for Private Cloud
 
 ## 2023
 
+### March 17th, 2023
+
+#### Mendix Operator v2.10.2 {#2.10.2}
+
+* We have updated components to use the latest dependency versions, in order to improve security score ratings for all container images.
+* We have fixed an issue where the Operator would continuously create and delete pods after a container's memory, CPU or ephemeral storage had been adjusted by the cluster. (Tickets 175836, 177443)
+* We have added an option to specify a custom limit of how many Mendix Runtime versions can be downloaded when using the [Registry Migration](/developerportal/deploy/private-cloud-migrating/) tool. (Ticket 178006)
+* We have reduced the scope granted to the `mendix-operator` and `mendix-agent` roles in Kubernetes. Instead of an `*` verb that includes all permissions, the roles are now more fine-grained.
+* We have fixed an issue where annotations would only apply to new OpenShift Routes. With this update, it is possible to add or modify annotations in existing OpenShift Routes.
+* We have fixed an issue where enabling the **Add credentials to pull secrets** option would not work when the Push URL and Pull URL were different. With this update, credentials are now added for the push and pull registries.
+* We have extended the options for configuring Google Cloud storage buckets. It is now possible to share a bucket between multiple environments.
+
 ### March 9th, 2023
 
 #### Deploy API Improvements