Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
27 commits
Select commit Hold shift + click to select a range
6147399
PMP 2.8.2 release notes
katarzyna-koltun-mx Nov 11, 2026
997371f
release notes
katarzyna-koltun-mx Nov 11, 2026
759b89e
updates
katarzyna-koltun-mx Nov 13, 2026
4b4d388
commit
katarzyna-koltun-mx Nov 13, 2026
f14f330
release notes updates
katarzyna-koltun-mx Nov 16, 2026
6cd64f7
updates
katarzyna-koltun-mx Nov 17, 2026
2e94bc4
Update pmp-key-vault-integration.md
katarzyna-koltun-mx Nov 17, 2026
839cd97
doc updates
katarzyna-koltun-mx Nov 18, 2026
ec4dd5b
Merge branch 'kk-pmp-relnotes282' of https://github.com/mendix/docs i…
katarzyna-koltun-mx Nov 18, 2026
8a9d3dd
updates
katarzyna-koltun-mx Nov 18, 2026
68d6f11
reconciling changes
katarzyna-koltun-mx Nov 19, 2026
8ee9048
second file
katarzyna-koltun-mx Nov 19, 2026
f59d253
third file
katarzyna-koltun-mx Nov 19, 2026
70e2bbd
moved the remaining changes
katarzyna-koltun-mx Nov 19, 2026
7f48d4b
vale
katarzyna-koltun-mx Nov 19, 2026
1359436
Build not supported for on-prem azure devops
katarzyna-koltun-mx Nov 19, 2026
88a183d
sme review
katarzyna-koltun-mx Nov 20, 2026
f9fe537
sme review
katarzyna-koltun-mx Nov 20, 2026
cdda0b5
vale
katarzyna-koltun-mx Nov 20, 2026
65f4a5c
sme review
katarzyna-koltun-mx Nov 20, 2026
9628632
added known issue
katarzyna-koltun-mx Nov 20, 2026
1c7547b
Log Settings more info
katarzyna-koltun-mx Nov 20, 2026
3bd1a3c
added configuration pattern
katarzyna-koltun-mx Nov 20, 2026
7dc26a7
adding api files
katarzyna-koltun-mx Nov 20, 2026
dc94dac
restoring the previous api file as this might not be the right format
katarzyna-koltun-mx Nov 20, 2026
649a633
known issues
katarzyna-koltun-mx Nov 20, 2026
d5e31fd
Added known issues
katarzyna-koltun-mx Nov 20, 2026
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
2 changes: 1 addition & 1 deletion content/en/docs/private-platform/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ The integration with Studio Pro does not currently support using the [Integratio
* Mendix developer experience hosted entirely within any virtual private cloud
* Support for SSO authentication for Private Mendix Platform and Studio Pro through your own identity provider (IdP)
* A private version of the Mendix Marketplace, with all contents hosted entirely within your Private Mendix Platform, accessible in-browser and directly from Studio Pro
* SCM repository support for GitLab, GitHub, Bitbucket and Azure DevOps Services, to be used as source code repository for your projects
* SCM repository support for GitLab, GitHub, Bitbucket, Azure DevOps Services and Azure DevOps Server, to be used as source code repository for your projects
* CI/CD capabilities out-of-the-box, with additional support for integrations with Jenkins, Kubernetes, and Azure DevOps; leverage our predefined templates or implement your own custom templates
* Operational capabilities such as basic log browsing and metrics through integrations with Loki and Grafana
* Governance features like application landscape management, marketplace administration, user group management, as well as various developer platform feature settings and action logs
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,10 @@ This document explains the configuration options available when configuring a Co

To configure the CI/CD pipeline, prepare the following:

* An Azure organization where you want to build your Mendix app.
* An Azure DevOps Services organization where you want to build your Mendix app. The Azure DevOps CI build utility runs on Microsoft-hosted agents and works with Azure DevOps Services only.

Building is not supported for the Azure DevOps Server (on-premises). Instead, use the Kubernetes build method. For more information, see [Azure DevOps Server Builds](/private-mendix-platform/configure-k8s/#azure-devops-server).

* An Azure blob or an AWS S3 endpoint where you can store the built MDA files.

## Configuring the CI/CD Pipeline
Expand Down
134 changes: 90 additions & 44 deletions content/en/docs/private-platform/configuration/pmp-configure-k8s.md

Large diffs are not rendered by default.

277 changes: 237 additions & 40 deletions content/en/docs/private-platform/configuration/pmp-version-control.md

Large diffs are not rendered by default.

1 change: 1 addition & 0 deletions content/en/docs/private-platform/pmp-prerequisites.md
Original file line number Diff line number Diff line change
Expand Up @@ -396,6 +396,7 @@ Private Mendix Platform must connect to services within your premises. Mandatory
| Version control | GitHub Enterprise Server | 3.6 or higher | Required for projects and collaboration |
| Version control | Bitbucket | Latest | Required for projects and collaboration |
| Version control | Azure DevOps Services | Cloud | Required for projects and collaboration |
| Version control | Azure DevOps Server (on-premises) | 2022.1 or higher | Required for projects and collaboration |
| CI/CD | Kubernetes | See See [Supported Cluster Types](#supported-clusters) | Default for CI/CD |
| CI/CD | Jenkins | 2.346.1 or newer, with support for the Docker agent | Required for CI/CD |
| CI/CD | Azure DevOps | Latest | Required for CI/CD |
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -614,7 +614,12 @@ When configuring secret management, keep in mind the following key points:
roleArn: "arn:aws:iam::123456789012:role/component-role"
# Step 2: Configure Secret Provider Class
secretProviderclass:
enable: true
enable: false
# Set to false to bring your own SecretProviderClass. The chart then skips rendering it and all provider parameters below are ignored. Your SecretProviderClass must be named after the MendixApp (<name>, or <name>-test when testApp is true), live in the same namespace and carry the annotation privatecloud.mendix.com/environment-class: "true"
create: true
database:
# When true, the chart doesn't request database-password from the secret store. The database is reached through the pod's identity (Azure Workload Identity or AWS IRSA)
passwordless: false
provider: "azure" # azure | aws | vault
# For Azure Key Vault
azureparameters:
Expand Down
4 changes: 4 additions & 0 deletions content/en/docs/private-platform/reference/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ linktitle: "Administrator Guide"
url: /private-mendix-platform/reference-guide/admin/
description: "Provides details on the features and functionality of the Private Mendix Platform that are available to administrators."
weight: 10
no_list: false
description_list: true
aliases:
- /private-mendix-platform-administration/
- /private-mendix-platform/administration/
Expand All @@ -28,3 +30,5 @@ Private Mendix Platform distinguishes between the following types of administrat
* Systems admin - This role primarily manages key settings which must be configured during the initial implementation, and which are rarely modified during normal operation. Settings relevant for systems admins are available in the [Settings](/private-mendix-platform/reference-guide/admin/system/#settings) section of the admin navigation menu.

{{< figure src="/attachments/private-platform/pmp-admin4.png" class="no-border" >}}

## Read More
26 changes: 26 additions & 0 deletions content/en/docs/private-platform/reference/manage/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
title: "Private Mendix Platform Functionalities - Company Administrators"
linktitle: "Company Administrators"
url: /private-mendix-platform/reference-guide/admin/company/
description: "Provides details on the features and functionality of the Private Mendix Platform that are available to company administrators."
weight: 10
no_list: false
description_list: true
---

## Introduction

In Private Mendix Platform, company administrators primarily manage business-as-usual tasks, for example inviting new users to an app, or approving Marketplace contents. Settings relevant for company admins are available in the [Manage](#manage) section of the admin navigation menu.

### Manage {#manage}

The **Manage** section of the administrator navigation menu contains settings relevant to your day-to-day tasks as a company admin. You can use it to manage your company apps, users and groups, Marketplace contents, and deployment clusters.

## Accessing the Configuration Settings

As a user with company administrator access rights, you can access the Private Mendix Platform configuration settings by performing the following steps:

1. Switch to Admin Mode by clicking the profile picture in the top right corner of the screen and selecting **Switch to Admin Mode**.
2. In the left navigation menu, open the **Manage** section.

## Read More
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
title: "Company Administrator Settings - Deployment"
linktitle: "Deployment"
url: /private-mendix-platform/admin-company/deployment/
description: "Provides details on the deployment settings that are available to company administrators."
weight: 30
---

## Introduction

In the **Deployment** section, administrators can manage existing clusters and register new ones.

## Cluster Manager

The **Cluster Manager** page allows administrators to configure clusters to be used in their devOps CI/CD pipelines. To configure a cluster, perform the following steps:

1. In **Switch to Admin Mode** > **Manage** > **Cluster Manager**, click **Register New Cluster**.
2. Configure the following values:

* **Cluster Name** – Specify a name for the cluster.
* **Cluster type** – Select the cluster type. **Kubernetes** is recommended.
* **API Server** – Specify your API server.
* **Token** – You must first create a service account, cluster role, and cluster role binding in the cluster, and then get the service account's token. For an example, see [Configuring Build Cluster Setting](/private-mendix-platform/configure-k8s/#build-cluster).
* **Enable Logging and Monitoring** – Specify whether Grafana and Prometheus monitoring should be enabled for this cluster.
* **Package Type** – For Kubernetes and Manual Production Deployment, select the type of package that will be uploaded to environments in this cluster.
* **S3 Endpoint** – For Kubernetes and Manual Production Deployment, specify the S3 endpoint, for example, `Cloud Object Storage - Amazon S3 - AWS`.
* **S3 Bucket Name** – For Kubernetes and Manual Production Deployment, specify the S3 bucket name, for example, `mybucket`.
* **Region** – For Kubernetes and Manual Production Deployment, specify the region, for example, `ap-southeast-1`.
* **Access Key ID** – For Kubernetes and Manual Production Deployment, this ID value is used to access the S3 bucket.
* **Secret Access Key** – For Kubernetes and Manual Production Deployment, this secret key value is used to access the S3 bucket.

3. Click **Save**.
4. Click the newly created cluster and expand it, and then click **Retrieve Namespace(s)** to retrieve all the namespace and storage plans, or **Manually Register Namespace**.

Namespaces without any storage plan are skipped. This step requires the Mendix Operator to be installed and configured. You can repeat this step as required to retrieve additional namespaces.

5. After the cluster is registered, create environments with the cluster, namespace and plans.

### Configuring CI/CD Pipelines with Manual Approval {#manual-deployment}

If your production and development environments must be fully air-gapped and separated from each other, and you want to limit the ability to deploy packages to either selected users or an automated pipeline with manual approval, you can configure your cluster type to be **Manual Production Deployment**.

Selecting this option allows you to specify an S3 bucket. This bucket is then used as the destination where the deployment package is uploaded at the end of the pipeline, instead of being deployed to the production environment. Designated approvers can then retrieve the package from the S3 bucket and manually deploy it to the target environment.
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
---
title: "Company Administrator Settings - Marketplace"
linktitle: "Marketplace"
url: /private-mendix-platform/admin-company/marketplace/
description: "Provides details on the Marketplace configuration settings that are available to company administrators."
weight: 20
---

## Introduction

In the **Marketplace** section, administrators can manage various settings related to the content available on the Private Platform Marketplace. The Private Platform Marketplace is a local version of [Mendix Marketplace](/appstore/), enclosed entirely within the Private Platform. Developers in your organization can also create their own modules, connectors, and sample apps, and share them on the Private Platform Marketplace to make them available to other users.

As the administrator, you can perform the following actions:

## Content Management {#content}

In the **Content Management** tab, you can view the Marketplace content that your users have already published, as well as any items which are pending approval, or which have been rejected.

{{< figure src="/attachments/private-platform/pmp-admin7.png" class="no-border" >}}

You can click on an item to view more information about it, download, approve, or delete it.

## Taxonomy Management

In the **Taxonomy Management** tab, you can configure the supported Studio Pro versions and sub-categories that your users can select when creating Marketplace content. You can also view and edit the available licenses.

{{< figure src="/attachments/private-platform/pmp-admin8.png" class="no-border" >}}

### Supported Versions

The versions listed on the **Supported Versions** page indicate the Mendix Studio Pro versions that a Marketplace content item is compatible with. Users can select these versions from a list when uploading new Marketplace content.

### Licenses

The **Licenses** tab allows administrators to specify the licenses that are available to their apps. To add a new license, click **New License** and specify the following values:

* **Name** – Name of the license
* **URL** – URL at which the license can be accessed
* **Contents** – Optional additional information about the license.

### App Categories

In the **App Categories** tab, you can view the predefined categories that users can specify for their Marketplace content items. You can also add custom categories, for example, for Marketplace contents related to a specific project.

Predefined app categories cannot be edited or deleted. To edit or delete a custom category, click the **Action** menu, and then select one of the available options.

## Import Content

You can populate your private Marketplace with contents by importing a zip file that contains the content packages along with a *package.json* file. You can upload the file from a Content Delivery Network, or manually from your local machine.

{{< figure src="/attachments/private-platform/pmp-admin9.png" class="no-border" >}}

## Upload Marketplace Bundle {#manual-upload}

To manually upload a content bundle from your own computer, perform the following steps:

1. Download the Marketplace Bundle with contents available in a zip file. If you do not have access to the bundle, contact your Mendix point of contact.
2. In the **Import Content** > **Upload Marketplace Bundle** tab, drag and drop the file that you want to upload.

* The file must be in *zip* format.
* The file must not be larger than 2048 MB.
* Your infrastructure must support the upload of large files (up to 2048MB).
* You should also have at least 40 GB available disk space to account for temporary files.

3. Click **Import Marketplace Bundle components**.

{{< figure src="/attachments/private-platform/pmp-config1.png" class="no-border" >}}

4. To view the progress of your upload, click **View Task Queue**.

{{% alert color="info" %}}
If you are experiencing high latency during manual uploads, you can increase the timeouts. For example, for nginx, you can perform the following commands:

```text
nginx.ingress.kubernetes.io/client-header-timeout: "300"
nginx.ingress.kubernetes.io/proxy-connect-timeout: "300"
nginx.ingress.kubernetes.io/proxy-read-timeout: "300"
nginx.ingress.kubernetes.io/proxy-send-timeout: "300"
```

{{% /alert %}}

## Import from CDN

To import content from a Content Delivery Network, follow these steps:

1. Ensure that your system administrator has [configured the Marketplace import bundle URL](/private-mendix-platform/reference-guide/admin/system/#configure-import).
2. In the **Import Content** > **Import from CDN** tab, view and download the available content items.
Loading
Loading