Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -42,8 +42,18 @@ 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 register names of Storage Plans) |

{{% 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 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, 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}

Expand Down Expand Up @@ -174,16 +184,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 %}}
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -952,7 +952,7 @@ the Operator will use the `<region>` 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}

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,20 @@ For information on the current status of deployment to Mendix on Kubernetes and

## 2026

### November 3, 2026

#### Mendix Operator 2.29.0 {#2.29.0}

* 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.

### October 22, 2026

#### Portal Improvements
Expand Down
Loading