From 869e789f526c251ca14858443bfeb546323ff514 Mon Sep 17 00:00:00 2001 From: Dmitrii Zolotukhin Date: Wed, 28 Oct 2026 15:09:07 +0100 Subject: [PATCH 1/6] Updated Release Notes for MxOK 2.29.0. * Updated supported Kubernetes versions. * Explained deprecation of ubi8 and the private-cloud.registry.mendix.com container registry. * Fixed Storage Plans documentation showing all paragraphs numbered as 0, 0.0 etc. --- .../private-cloud-cluster/_index.md | 20 +++++++++++++++---- .../private-cloud-storage-plans.md | 2 +- .../private-cloud-supported-environments.md | 4 ++-- .../deployment/mendix-for-private-cloud.md | 20 +++++++++++++++++++ 4 files changed, 39 insertions(+), 7 deletions(-) diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md index d27413e1a41..f7d3eb66a0a 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md @@ -42,8 +42,20 @@ All services listed in the table below use the HTTPS protocol (port 443). |-----|-------------| | `https://interactor-bridge.private-cloud.api.mendix.com` | Websocket based main communication API | | `https://package-store-prod-2.s3-accelerate.amazonaws.com/` | Registry for downloading MDA artifacts | -| `https://private-cloud.registry.mendix.com` | Docker registry for downloading Runtime base images | +| `https://registry.mendix.com` | OCI registry with Mendix Operator container images | +| `https://private-cloud.registry.mendix.com` | Legacy OCI registry with Mendix Operator container images | | `https://subscription-api.mendix.com` | Service to verify call-home license | +| `https://privatecloud.mendixcloud.com` | Private Cloud Portal (used to submit names of Storage Plans) | + +{{% alert color="info" %}} +The `private-cloud.registry.mendix.com` container registry will be decomissioned on August 1, 2027. + +Starting from Mendix Operator version 2.29.0, new namespaces will be using `registry.mendix.com/private-cloud` by default. +If your network blocks access to `https://registry.mendix.com`, it's possible to manually switch to the legacy registry by running +the `mxpc-cli` **Configuration Tool** with a `--registry private-cloud.registry.mendix.com` flag. + +In Helm chart installations, switching to the `private-cloud.registry.mendix.com` registry is possible by using the **Custom OCI Registry** configuration option. +{{% /alert %}} ## Creating a Cluster and Namespace {#create-cluster-namespace} @@ -174,16 +186,16 @@ spec: At the moment, the `baseOSImageTagTemplate` can be set to one of the following values: -* `ubi8-1-jre{{.JavaVersion}}-entrypoint` - to use Red Hat UBI 8 Micro images; this option can be used for some cases where backward compatibility is needed. +* `ubi8-1-jre{{.JavaVersion}}-entrypoint` - to use Red Hat UBI 8 Micro images; this is a legacy option and will no longer be supported after March 1, 2027. * `ubi9-1-jre{{.JavaVersion}}-entrypoint` - to use Red Hat UBI 9 Micro images; this is the default option. * `hi-1-jre{{.JavaVersion}}-entrypoint` - to use [Red Hat Hardened Images](https://www.redhat.com/en/products/hardened-images) {{% alert color="info" %}} -If an app's MDA was built using a newer Java version, Mendix Operator 2.15.0 (and newer versions) will detect this and use a base image with the same major Java version that was used to build the MDA. Because of that, Java 17 or Java 21-based applications should use the Operator in version 2.15.0 or above. +If an app's MDA was built using a newer Java version, Mendix Operator 2.15.0 (and newer versions) will detect this and use a base image with the same major Java version that was used to build the MDA. Because of that, Java 17, Java 21 or Java 25-based applications should use the Operator in version 2.15.0 or above. {{% /alert %}} {{% alert color="info" %}} -Red Hat Hardened Images do not provide images for Java 8, 11, or 17. Only Java 21 is supported at the moment. +Red Hat Hardened Images do not provide images for Java 8, 11, or 17. Only Java 21 and 25 are supported at the moment. To use Hardened Images, upgrade to Mendix 11, or any supported LTS version of Mendix. {{% /alert %}} diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md index f1d230801f7..d0f0c274311 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-storage-plans.md @@ -952,7 +952,7 @@ the Operator will use the `` part. * If the S3 bucket endpoint does not match this format, the Mendix Operator will use a default `us-east-1` region, as this works with most S3-compatible buckets like [Minio](#blob-minio) and [Google Cloud Storage](#blob-gcp-storage-bucket). In some scenarios (legacy or custom S3 endpoints), this autodetection might not work correctly. In this case, you can manually specify the S3 bucket region by setting the [com.mendix.storage.s3.Region](/refguide/custom-settings/#commendixstorages3Region) Custom Runtime Setting. A manually specified `com.mendix.storage.s3.Region` will override the autodetected bucket region. -{{% /alert %}}. +{{% /alert %}} #### Create Account with Existing Policy {#s3-create-account-existing-policy} diff --git a/content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md b/content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md index df6fbf04a8e..79e03e31b42 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-supported-environments.md @@ -46,8 +46,8 @@ The Mendix Operator automatically detects when it is running in Azure Government Mendix on Kubernetes Operator `v2.*.*` is the latest version which officially supports: -* Kubernetes versions 1.19 through 1.36 -* OpenShift 4.6 through 4.21 +* Kubernetes versions 1.19 through 1.37 +* OpenShift 4.6 through 4.22 {{% alert color="warning" %}} Kubernetes 1.22 is a [new release](https://kubernetes.io/blog/2021/08/04/kubernetes-1-22-release-announcement/) which removes support for several deprecated APIs and features. diff --git a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md index ded7fe8fca5..867d3f5e9ae 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -12,6 +12,26 @@ For information on the current status of deployment to Mendix on Kubernetes and ## 2026 +### November ???, 2026 + +#### Mendix Operator 2.29.0 {#2.29.0} + +* New Mendix on Kubernetes namespaces will be using a new `registry.mendix.com/private-cloud` container registry by default. + The new registry is based on a scalable, geo-distributed architecture and will increase image downloads speeds in certain regions. +* We have fixed an issue where applying pod labels from the Private Cloud Portal would cause Azure Workload Identity authentication to fail. (Ticket 290587) +* We have fixed an issue with IAM authentication in AWS China regions. (Ticket 290116) +* We have updated components to use Go 1.27 and the latest dependency versions in order to improve security score ratings for container images. + +#### Deprecations + +* Mendix on Kubernetes components are migrating from the `private-cloud.registry.mendix.com` container registry to `registry.mendix.com/private-cloud`. + The `private-cloud.registry.mendix.com` registry will remain available and will continue to receive new images until August 1, 2027. + It is possible to specify which container registry to use during installation of the Mendix Operator. +* `ubi8` runtime base images will no longer receive updates after March 1, 2027. + `ubi9` and `hi` (Red Hat Hardened Images) will continue to be maintained and supported. + For more information on switching to these images, see the [Runtime Base Image](/developerportal/deploy/private-cloud-cluster/#runtime-base-image) configuration. + The Helm chart UI allows to choose the base image from the dropdown. + ### October 22, 2026 #### Portal Improvements From 851312e11201202b90e60d1ca390018049915bad Mon Sep 17 00:00:00 2001 From: Dmitrii Zolotukhin Date: Wed, 28 Oct 2026 15:26:45 +0100 Subject: [PATCH 2/6] Reworded notes. --- .../deployment/private-cloud/private-cloud-cluster/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md index f7d3eb66a0a..9efa20b6a4d 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md @@ -45,7 +45,7 @@ All services listed in the table below use the HTTPS protocol (port 443). | `https://registry.mendix.com` | OCI registry with Mendix Operator container images | | `https://private-cloud.registry.mendix.com` | Legacy OCI registry with Mendix Operator container images | | `https://subscription-api.mendix.com` | Service to verify call-home license | -| `https://privatecloud.mendixcloud.com` | Private Cloud Portal (used to submit names of Storage Plans) | +| `https://privatecloud.mendixcloud.com` | Private Cloud Portal (used to register names of Storage Plans) | {{% alert color="info" %}} The `private-cloud.registry.mendix.com` container registry will be decomissioned on August 1, 2027. From a3144f5d3a9c67bbd8b21d30a6d9d7eeecf2b643 Mon Sep 17 00:00:00 2001 From: Dmitrii Zolotukhin Date: Thu, 29 Oct 2026 17:27:17 +0100 Subject: [PATCH 3/6] Fixed spelling. --- .../deployment/private-cloud/private-cloud-cluster/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md index 9efa20b6a4d..83dca049ed2 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md @@ -48,7 +48,7 @@ All services listed in the table below use the HTTPS protocol (port 443). | `https://privatecloud.mendixcloud.com` | Private Cloud Portal (used to register names of Storage Plans) | {{% alert color="info" %}} -The `private-cloud.registry.mendix.com` container registry will be decomissioned on August 1, 2027. +The `private-cloud.registry.mendix.com` container registry will be decommissioned on August 1, 2027. Starting from Mendix Operator version 2.29.0, new namespaces will be using `registry.mendix.com/private-cloud` by default. If your network blocks access to `https://registry.mendix.com`, it's possible to manually switch to the legacy registry by running From f9b593c2f90f26d54e487b9234c8a2bc65d806f0 Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Thu, 29 Oct 2026 17:56:48 +0100 Subject: [PATCH 4/6] Update _index.md --- .../private-cloud/private-cloud-cluster/_index.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md index 83dca049ed2..bbe88d4f09f 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md @@ -50,11 +50,9 @@ All services listed in the table below use the HTTPS protocol (port 443). {{% alert color="info" %}} The `private-cloud.registry.mendix.com` container registry will be decommissioned on August 1, 2027. -Starting from Mendix Operator version 2.29.0, new namespaces will be using `registry.mendix.com/private-cloud` by default. -If your network blocks access to `https://registry.mendix.com`, it's possible to manually switch to the legacy registry by running -the `mxpc-cli` **Configuration Tool** with a `--registry private-cloud.registry.mendix.com` flag. +Starting from Mendix Operator version 2.29.0, new namespaces will use `registry.mendix.com/private-cloud` by default. If your network blocks access to `https://registry.mendix.com`, you can manually switch to the legacy registry by running the `mxpc-cli` **Configuration Tool** with a `--registry private-cloud.registry.mendix.com` flag. -In Helm chart installations, switching to the `private-cloud.registry.mendix.com` registry is possible by using the **Custom OCI Registry** configuration option. +In Helm chart installations, you can switch to the `private-cloud.registry.mendix.com` registry by using the **Custom OCI Registry** configuration option. {{% /alert %}} ## Creating a Cluster and Namespace {#create-cluster-namespace} From ef1de45cb1d6599572631893acf942e681ad8c19 Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Thu, 29 Oct 2026 19:31:45 +0100 Subject: [PATCH 5/6] Update mendix-for-private-cloud.md --- .../deployment/mendix-for-private-cloud.md | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md index 867d3f5e9ae..10c42eed2fd 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -12,25 +12,19 @@ For information on the current status of deployment to Mendix on Kubernetes and ## 2026 -### November ???, 2026 +### November 2, 2026 #### Mendix Operator 2.29.0 {#2.29.0} -* New Mendix on Kubernetes namespaces will be using a new `registry.mendix.com/private-cloud` container registry by default. - The new registry is based on a scalable, geo-distributed architecture and will increase image downloads speeds in certain regions. +* New Mendix on Kubernetes namespaces will use a new `registry.mendix.com/private-cloud` container registry by default. The new registry is based on a scalable, geo-distributed architecture and will increase image downloads speeds in certain regions. * We have fixed an issue where applying pod labels from the Private Cloud Portal would cause Azure Workload Identity authentication to fail. (Ticket 290587) * We have fixed an issue with IAM authentication in AWS China regions. (Ticket 290116) * We have updated components to use Go 1.27 and the latest dependency versions in order to improve security score ratings for container images. #### Deprecations -* Mendix on Kubernetes components are migrating from the `private-cloud.registry.mendix.com` container registry to `registry.mendix.com/private-cloud`. - The `private-cloud.registry.mendix.com` registry will remain available and will continue to receive new images until August 1, 2027. - It is possible to specify which container registry to use during installation of the Mendix Operator. -* `ubi8` runtime base images will no longer receive updates after March 1, 2027. - `ubi9` and `hi` (Red Hat Hardened Images) will continue to be maintained and supported. - For more information on switching to these images, see the [Runtime Base Image](/developerportal/deploy/private-cloud-cluster/#runtime-base-image) configuration. - The Helm chart UI allows to choose the base image from the dropdown. +* Mendix on Kubernetes components are migrating from the `private-cloud.registry.mendix.com` container registry to `registry.mendix.com/private-cloud`. The `private-cloud.registry.mendix.com` registry will remain available and will continue to receive new images until August 1, 2027. It is possible to specify which container registry to use during installation of the Mendix Operator. +* `Ubi8` runtime base images will no longer receive updates after March 1, 2027. `Ubi9` and `hi` (Red Hat Hardened Images) will continue to be maintained and supported. For more information on switching to these images, see the [Runtime Base Image](/developerportal/deploy/private-cloud-cluster/#runtime-base-image) configuration. The Helm chart UI allows to choose the base image from the dropdown. ### October 22, 2026 From 58011a003e4c69f292da81bd72b274b87fc6d639 Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Tue, 3 Nov 2026 14:32:06 +0100 Subject: [PATCH 6/6] Update mendix-for-private-cloud.md --- .../en/docs/releasenotes/deployment/mendix-for-private-cloud.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md index 10c42eed2fd..61b78eee0de 100644 --- a/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md +++ b/content/en/docs/releasenotes/deployment/mendix-for-private-cloud.md @@ -12,7 +12,7 @@ For information on the current status of deployment to Mendix on Kubernetes and ## 2026 -### November 2, 2026 +### November 3, 2026 #### Mendix Operator 2.29.0 {#2.29.0}