diff --git a/content/en/docs/control-center/apps/deployed-apps.md b/content/en/docs/control-center/apps/deployed-apps.md index 1c03aa9513a..a21e2b9cd70 100644 --- a/content/en/docs/control-center/apps/deployed-apps.md +++ b/content/en/docs/control-center/apps/deployed-apps.md @@ -89,7 +89,7 @@ The list shows the following information: ## Apps with License Keys {#apps-license-keys} -The **Apps with License Keys** tab provides an overview of all apps for which license keys have been issued to their respective Technical Contacts. This includes all your apps deployed on Mendix on Kubernetes Standalone, Docker, Cloud Foundry buildpack, and on-premises environments. You can find the latest version of license keys for these app environments here. +The **Apps with License Keys** tab provides an overview of all apps for which license keys have been issued to their respective Technical Contacts. This includes all your apps deployed on Docker, Cloud Foundry buildpack, and on-premises environments. You can find the latest version of license keys for these app environments here. License keys are aligned with your Mendix contracts and need to be applied by you to each app. Every app environment (such as test, acceptance, and production) requires its own license key. diff --git a/content/en/docs/deployment/general/subscription-management/licensing-apps.md b/content/en/docs/deployment/general/subscription-management/licensing-apps.md index 4ca4495f554..530d2392ada 100644 --- a/content/en/docs/deployment/general/subscription-management/licensing-apps.md +++ b/content/en/docs/deployment/general/subscription-management/licensing-apps.md @@ -95,18 +95,14 @@ To license an Insights Hub app, you need to provide your **License ID** and **Li ### Mendix on Kubernetes -To license a Mendix app on Mendix on Kubernetes, you need to supply a **Subscription Secret** or license credentials for your app. See below for how it can be added to either a Connected or Standalone cluster. +To license a Mendix app on Mendix on Kubernetes, you need to supply a **Subscription Secret** or license credentials for your app. See below for how it can be added to a cluster. In addition to the licenses for your apps, you will also need to license the Mendix Operator, which helps deploy your app to a Mendix on Kubernetes environment. For details on the Mendix Operator license, see [Licensing Mendix on Kubernetes](/developerportal/deploy/private-cloud/#licensing). -#### Mendix on Kubernetes Connected +#### Adding the Subscription Secret You can add the subscription secret when creating an environment on Mendix on Kubernetes. You can also add or change the subscription secret on the **Environment Details** page of the environment you wish to license. For more information, see the [Change Subscription Secret](/developerportal/deploy/private-cloud-deploy/#license-mendix) section of *Deploying a Mendix App to a Mendix on Kubernetes Cluster*. -#### Mendix on Kubernetes Standalone - -You will need to add the license credentials and configure the license in the Mendix Custom Resource (CR) for your Mendix on Kubernetes environment. For more information, see the [Editing the CR](/developerportal/deploy/private-cloud-operator/#edit-cr) section of *Using Command Line to Deploy a Mendix App to a Mendix on Kubernetes Cluster*. - ### Cloud Foundry{#cloudfoundry} The following steps describe activating the license for deployments using the Cloud Foundry Buildpack. If you are deploying using Portable App Distribution, follow the steps in the [Portable App Distribution](#portableappdistribution) section below. diff --git a/content/en/docs/deployment/private-cloud/_index.md b/content/en/docs/deployment/private-cloud/_index.md index 071db05ecd9..db9316b1011 100644 --- a/content/en/docs/deployment/private-cloud/_index.md +++ b/content/en/docs/deployment/private-cloud/_index.md @@ -12,8 +12,6 @@ Mendix on Kubernetes allows you to deploy and manage your Mendix apps in a Kuber Your organization may have a requirement to use a private cloud, perhaps as part of a multi-cloud strategy. This could be because of legal requirements or a desire to have complete control over your data. Mendix on Kubernetes allows you to do this while keeping the familiar components of Docker and Kubernetes. -You can use Mendix on Kubernetes with the *connected* option to keep the simplicity of one-click deployments from the Mendix Portal, or utilize the *standalone* Mendix Operator to deploy Mendix apps through your own DevOps process, which is particularly useful for private clouds with an *air-gap* isolating them from the internet. See [Connected and Standalone Clusters](#connected-standalone), below, for more information. - Please see [Supported Providers](/developerportal/deploy/private-cloud-supported-environments/) for a list of platforms supported by Mendix on Kubernetes. There are two steps required to achieve this, listed below. @@ -37,41 +35,33 @@ To deploy your app, you have two options: When you deploy through the Mendix Portal, this can be done by any Mendix user who has been given the appropriate rights to the cluster which has been registered. -## Connected and Standalone Clusters{#connected-standalone} +## Clusters{#clusters} To allow you to manage the deployment of your apps to Red Hat OpenShift and Kubernetes, you first need to register a cluster in the Mendix Portal. This will provide you with the information you need to deploy the **Mendix Operator** in your cluster. If you have chosen a *connected* cluster, the **Mendix Gateway Agent** will also be deployed. Once the Mendix Operator is deployed to your cluster, you can use it to configure the resources which will be used by your apps. -You then have two options, depending on whether you have chosen to create a *connected* cluster or a *standalone* cluster. - -### Connected Architecture +### Architecture -If you have chosen to register a connected cluster, the Mendix Gateway Agent will create a link to the **Environments** pages of your Mendix app through the **Interactor**. This is a secure bi-directional communication channel which is initiated from the Mendix Gateway Agent running on the cluster. +The Mendix Gateway Agent will create a link to the **Environments** pages of your Mendix app through the **Interactor**. This is a secure bi-directional communication channel which is initiated from the Mendix Gateway Agent running on the cluster. Using this channel, any Mendix user who has been given the correct authority can pass instructions to the Mendix Operator and receive status information about the cluster. This includes instructions needed to deploy an app, or to configure the environment. {{< figure src="/attachments/deployment/private-cloud/mx4pc-architecture.png" class="no-border" >}} -### Standalone Architecture - -If you have chosen to register a standalone cluster, then all communication with the Mendix Operator will be through instructions which are made directly through the Kubernetes API. These can be made manually, but are generally performed by your CI/CD pipeline. In this case, you will also have to have local source control of the Mendix app deployment packages to ensure that the deployment process can discover them. - -{{< figure src="/attachments/deployment/private-cloud/mx4pc-standalone-architecture.png" class="no-border" >}} - ## Product Capability Comparison -The table below shows the differences between the capabilities for apps deployed to Mendix Cloud, Mendix on Kubernetes Connected, and Mendix on Kubernetes Standalone. +The table below shows the differences between the capabilities for apps deployed to Mendix Cloud and Mendix on Kubernetes. -| Capability | Mendix Cloud | Mendix on Kubernetes Connected | Mendix on Kubernetes Standalone | -| --- | --- | --- | --- | -| Environment provisioning | Fully automated | Provisioned with database and blob storage provided by the customer | Provisioned with database and blob storage provided by the customer| -| Environment configuration
*For example, constants and scheduled event* | Mendix Portal | Mendix Portal | Custom Resources via Mendix Operator | -| Mendix app/deployment package deployment | Mendix Portal and Studio Pro | Mendix Portal and Studio Pro | Custom Resources via Mendix Operator
*normally combined in a CI/CD pipeline* | -| Backup and restore | Mendix Portal | Services supplied by the database server and file storage used¹ | Services supplied by the database server and file storage used¹ | -| Monitoring | Mendix Portal | App metrics sent to a Prometheus-compatible monitoring tool | App metrics sent to a Prometheus-compatible monitoring tool | -| App logs | Mendix Portal | Prints app logs to `stdout` | Prints app logs to `stdout` | -| Remote debugging | Mendix Portal + Studio Pro | Mendix Portal + Studio Pro | Not supported | +| Capability | Mendix Cloud | Mendix on Kubernetes | +| --- | --- | --- | +| Environment provisioning | Fully automated | Provisioned with database and blob storage provided by the customer | +| Environment configuration
*For example, constants and scheduled event* | Mendix Portal | Mendix Portal | +| Mendix app/deployment package deployment | Mendix Portal and Studio Pro | Mendix Portal and Studio Pro | +| Backup and restore | Mendix Portal | Services supplied by the database server and file storage used¹ | +| Monitoring | Mendix Portal | App metrics sent to a Prometheus-compatible monitoring tool | +| App logs | Mendix Portal | Prints app logs to `stdout` | +| Remote debugging | Mendix Portal + Studio Pro | Mendix Portal + Studio Pro | {{% alert color="info" %}} ¹ No backup or restore functionality is installed automatically with Mendix on Kubernetes. You will need to choose and deploy your own solution, dependent on your choice of database, file storage, and cloud platform. @@ -90,10 +80,6 @@ All of those containers, including the sidecar containers, have specific resourc The Mendix container is specified per app in the portal. You can update the resource allocation in the [Mendix App CR](/developerportal/deploy/private-cloud-operator/#edit-cr). The m2ee-sidecar container's resources are specified in the [OperatorConfiguration CR](/developerportal/deploy/private-cloud-cluster/#resource-definition-ocm). -{{% alert color="info" %}} -If the app is running in Standalone mode and its MendixApp CR does not have any resources assigned in the MendixApp CR specification resources, the Mendix Operator will use the value of *OperatorConfiguration* CR's *spec.runtimeResources* instead. -{{% /alert %}} - If the customer decided to use a [Vertical Pod autoscaler](/developerportal/deploy/private-cloud-cluster/#vertical-pod-autoscaling), the autoscaler can override any pod or container resources. When a user sets CPU and memory limits, the JVM (JRE 8u191+) will automatically detect the container requests and limits, and automatically set Java memory limits based on the container details. @@ -126,7 +112,7 @@ You can request an Operator license by doing the following: * The name of your company (if requesting on behalf of a client, enter the name of their company). * License Type: Operator - * The Mendix on Kubernetes architecture type. See [Connected and Standalone Clusters](#connected-standalone), above, for more information — optionally, leave additional information in the **comment** field + * The Mendix on Kubernetes architecture type. See [Clusters](#clusters), above, for more information — optionally, leave additional information in the **comment** field * The namespace (or namespaces) for which you want to request an Operator license 5. Save the request. @@ -151,7 +137,7 @@ You can request a Runtime license by doing the following: * The name of your company (if requesting on behalf of a client, enter the name of their company). * License Type: Runtime - * The Mendix on Kubernetes architecture type. See [Connected and Standalone Clusters](#connected-standalone), above, for more information — optionally, leave additional information in the **comment** field + * The Mendix on Kubernetes architecture type. See [Clusters](#clusters), above, for more information — optionally, leave additional information in the **comment** field * If "Connected" please provide the namespace (or namespaces) for which you are requesting the runtime license (or licenses) 5. Save the request. @@ -172,7 +158,7 @@ You can also request for both the Operator and Runtime license within the same r * The name of your company (if requesting on behalf of a client, enter the name of their company). * License Type: Operator and Runtime - * The Mendix on Kubernetes architecture type. See [Connected and Standalone Clusters](#connected-standalone), above, for more information — optionally, leave additional information in the **comment** field + * The Mendix on Kubernetes architecture type. See [Clusters](#clusters), above, for more information — optionally, leave additional information in the **comment** field * The namespace (or namespaces) for which you want to request an Operator license ### Activating Your License (or Licenses) @@ -181,11 +167,11 @@ You can also request for both the Operator and Runtime license within the same r If your app is able to connect to the internet to contact the Mendix license server, you will receive a **Subscription Secret** from Mendix Support. -If your app is **Connected** to the Mendix Portal, you can enter the subscription secret [in the Mendix Portal](/developerportal/deploy/private-cloud-deploy/#license-mendix) +If your app is connected to the Mendix Portal, you can enter the subscription secret [in the Mendix Portal](/developerportal/deploy/private-cloud-deploy/#license-mendix) -#### Standalone & Offline Mendix on Kubernetes Apps{#activate-offline} +#### Offline Mendix on Kubernetes Apps{#activate-offline} -If your app is **Standalone** or unable to contact the Mendix license server, you will receive a **LicenseId** and a **LicenseKey**. You will have to apply these by [editing the CR](/developerportal/deploy/private-cloud-operator/#edit-cr) in the cluster. +If your app is or unable to contact the Mendix license server, you will receive a **LicenseId** and a **LicenseKey**. You will have to apply these by [editing the CR](/developerportal/deploy/private-cloud-operator/#edit-cr) in the cluster. #### Private Cloud Licensing Manager 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 855f60a830e..5bdd589ff39 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 @@ -73,7 +73,7 @@ All services listed in the table below use the HTTPS protocol (port 443). {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/create-cluster.png" class="no-border" >}} -### Adding a Namespace for Connected Cluster {#add-namespace} +### Adding a Namespace {#add-namespace} You now need to add a namespace to your cluster. Your cluster can contain several namespaces, see [Containerized Mendix App Architecture](#containerized-architecture), below for more information. @@ -89,9 +89,7 @@ To add a namespace, do the following: {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/namespace-details.PNG" class="no-border" >}} -3. Enter the following details: - * **Namespace** – this is the namespace in your platform; this must conform to the namespace naming conventions of the cluster: all lower-case with hyphens allowed within the name - * **Installation type** – if you want to create environments and deploy your app from the [Mendix Portal](/developerportal/deploy/private-cloud-deploy/), choose **Connected**, but if you only want to control your deployments through the Mendix Operator using the [CLI](/developerportal/deploy/private-cloud-operator/), choose **Standalone** +3. Specify a **Namespace** in your platform. This must conform to the namespace naming conventions of the cluster: all lower-case with hyphens allowed within the name. 4. Click **Done** to create the namespace. @@ -99,34 +97,6 @@ To add a namespace, do the following: {{% alert color="warning" %}} If you have selected a *Connected Installation Type* please verify that the [Connected Environment Pre-requisites](#prerequisites-connected) are configured. {{% /alert %}} -### Adding a Namespace for Standalone Cluster {#add-standalone-namespace} - -If you would like to add a namespace to be added in the Standalone cluster, do the following: - -1. Click **Details** ({{% icon name="notes-paper-text" %}}) on the top right of the page: - - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/empty-cluster.png" class="no-border" >}} - - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/ClusterDetails.png" class="no-border" >}} - -2. Click **Add Namespace**. - - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/namespace-details-standalone.png" class="no-border" >}} - -3. Enter the following details: - - * **Namespace** – This is the namespace in your platform; this must conform to the namespace naming conventions of the cluster: all lower-case with hyphens allowed within the name. - * **Installation type** – Choose **Standalone**. - -4. Click **Next**. -5. Once you click on **Next**, you will be redirected to the Installation pop up page from where you can download the mxpc-cli and get the command to install the namespace in the cluster. - - {{< figure src="/attachments/deployment/private-cloud/private-cloud-cluster/standalone_downloadcli.png" class="no-border" >}} - - For existing namespaces, if you would like to download the executables for mxpc-cli, you can go [here](https://privatecloud.mendixcloud.com/rest/internal/v1/mxpc-cli?operatorVersion=latest) - - In above page, once you do a JSON format, you will get the links for mxpc-cli for different available versions. - ## Installing and Configuring the Mendix Operator {#install-operator} You can install and run the Mendix Operator in either Global or Standard mode. In Global mode, the Operator is installed once for all available namespaces, whereas in Standard mode, it is installed separately for each namespace where a Mendix app is deployed. For more information, see: diff --git a/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md b/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md index 952b9d2e37a..39667fa9de5 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-license-manager.md @@ -17,7 +17,7 @@ Mendix highly recommends that you upgrade to the latest available version to ens When deploying your Mendix app for production use, it needs to be licensed. This removes the restrictions which are placed on unlicensed apps. For more information, see [Licensing Mendix on Kubernetes](/developerportal/deploy/private-cloud/#licensing) in the *Private Cloud* documentation. -Apps which are deployed to Mendix Cloud have access to the internet and have licenses which work on a subscription basis, contacting the Mendix license server to validate the license. This method is not appropriate for apps which are deployed using Mendix on Kubernetes, and may even be in standalone mode and not connected to the internet (air-gapped). +Apps which are deployed to Mendix Cloud have access to the internet and have licenses which work on a subscription basis, contacting the Mendix license server to validate the license. This method is not appropriate for apps which are deployed using Mendix on Kubernetes. Rather than having to apply and update licenses for each environment individually, the Mendix **Mendix on Kubernetes License Manager** (PCLM) provides a repository of offline Mendix licenses to enable you to manage these centrally. This reduces the possibility of errors, and enables the production of license usage reports. @@ -27,7 +27,7 @@ The PCLM runs as a Kubernetes service on your cluster. This means that it can be To install and use the PCLM, you need the following prerequisites: -* A Mendix on Kubernetes **Standalone** cluster +* A Mendix on Kubernetes cluster * Mendix Operator in version 2.11.0 or above * Administrative rights to a Kubernetes namespace to install PCLM server (a dedicated namespace is recommended). This can be within your Mendix on Kubernetes cluster, or in another cluster which is accessible over HTTP * A Postgres or SQLServer database server and within it: diff --git a/content/en/docs/deployment/private-cloud/private-cloud-monitor.md b/content/en/docs/deployment/private-cloud/private-cloud-monitor.md index 9e2554a8ede..2231532fabe 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-monitor.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-monitor.md @@ -323,7 +323,7 @@ Then restart the Mendix Operator. If you would like to enable Prometheus scraping only for a specific environment, you can add the Prometheus scraping annotations just for that environment. -#### Enable Scraping in Connected Mode +#### Enable Scraping 1. Go to the Cluster Manager page by clicking **Cluster Manager** in the top menu of the **Clouds** page of the Mendix Portal. @@ -351,31 +351,6 @@ If you would like to enable Prometheus scraping only for a specific environment, -#### Enable Scraping in Standalone Mode - -{{% alert color="warning" %}}Do not use this approach in Connected mode - any annotations you set this way will be overridden by annotations set in the Mendix on Kubernetes section of the Mendix Portal.{{% /alert %}} - -Open an environment's `MendixApp` CR [for editing](/developerportal/deploy/private-cloud-operator/#edit-cr) and add the following pod annotations: - -```yaml -apiVersion: privatecloud.mendix.com/v1alpha1 -kind: MendixApp -metadata: - name: example-mendixapp -spec: - # Existing configuration - # ... - runtimeDeploymentPodAnnotations: - # Existing annotations - # ... - # Add these new annotations: - prometheus.io/path: /metrics - prometheus.io/port: '8900' - prometheus.io/scrape: 'true' -``` - -Save and apply the changes. - ## Setting up a Grafana Dashboard Mendix on Kubernetes offers a reference dashboard that looks similar to Mendix Cloud [Metrics](/developerportal/operate/metrics/). @@ -518,7 +493,7 @@ This way, upgrading an older Mendix Operator will not change the way it generate To enable `compatibility` metrics mode, set the `mode` attribute to `compatibility`. In this mode, all other `runtimeMetricsConfiguration` attributes are ignored. -#### Enable Compatibility Metrics in Connected Mode +#### Enable Compatibility Metrics 1. Open your app in [Apps](https://sprintr.home.mendix.com/). 2. Go to the **Environments** page. @@ -542,33 +517,11 @@ In this mode, all other `runtimeMetricsConfiguration` attributes are ignored. {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-compatibility.png" class="no-border" >}} -#### Enable Compatibility Metrics in Standalone Mode - -{{% alert color="warning" %}}Do not use this approach in Connected mode. Any configuration you set this way will be overridden by the configuration set in the Mendix on Kubernetes section of the Mendix Portal.{{% /alert %}} - -Open an environment's `MendixApp` CR [for editing](/developerportal/deploy/private-cloud-operator/#edit-cr) and set the `mode` attribute in `runtimeMetricsConfiguration` to `compatibility`: - -```yaml -apiVersion: privatecloud.mendix.com/v1alpha1 -kind: MendixApp -metadata: - name: example-mendixapp -spec: - # Existing configuration - # ... - # Metrics configuration - runtimeMetricsConfiguration: - # Set mode to compatibility - mode: compatibility -``` - -Save and apply the changes. - ### Disable All Metrics Collection To completely disable metrics collection, delete the `runtimeMetricsConfiguration` block from the `OperatorConfiguration` CR, and update the environment to use the default metrics configuration. -#### Disable Metrics in Connected Mode +#### Disable Metrics 1. Open your app in [Apps](https://sprintr.home.mendix.com/). 2. Go to the **Environments** page. @@ -592,27 +545,6 @@ To completely disable metrics collection, delete the `runtimeMetricsConfiguratio {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-mode-default.png" class="no-border" >}} -#### Disable Metrics in Standalone Mode - -{{% alert color="warning" %}}Do not use this approach in Connected mode. Any configuration you set this way will be overridden by the configuration set in the Mendix on Kubernetes section of the Mendix Portal.{{% /alert %}} - -Open the environment's `MendixApp` CR [for editing](/developerportal/deploy/private-cloud-operator/#edit-cr) and delete the `runtimeMetricsConfiguration` block: - -```yaml -apiVersion: privatecloud.mendix.com/v1alpha1 -kind: MendixApp -metadata: - name: example-mendixapp -spec: - # Existing configuration - # ... - # Delete this runtimeMetricsConfiguration block - runtimeMetricsConfiguration: - ... -``` - -Save and apply the changes. - ### Native Metrics Mode To enable `native` metrics mode, set the `mode` attribute to `native`. @@ -628,7 +560,7 @@ If an environment has a manually assigned `Metrics.Registries` key, it will be u It is also possible to add extra tags (Prometheus labels) by specifying them in the [Metrics.ApplicationTags](/refguide/metrics/#application-tags) custom setting. -#### Enable Native Metrics in Connected Mode{#enable-native-metrics-connected-mode} +#### Enable Native Metrics {#enable-native-metrics-connected-mode} 1. Open your app in [Apps](https://sprintr.home.mendix.com/). 2. Go to the **Environments** page. @@ -661,7 +593,7 @@ It is also possible to add extra tags (Prometheus labels) by specifying them in {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/environment-metrics-apply.png" class="no-border" >}} -#### Configure additional Native Metrics options in Connected Mode +#### Configure Additional Native Metrics Options After an environment is [switched into native metrics mode](#enable-native-metrics-connected-mode), it is possible to configure additional options for that environment. @@ -692,45 +624,6 @@ After an environment is [switched into native metrics mode](#enable-native-metri {{< figure src="/attachments/deployment/private-cloud/private-cloud-monitor/private-cloud-metrics-apply.png" class="no-border" >}} -#### Enable Native Metrics in Standalone Mode - -{{% alert color="warning" %}}Do not use this approach in Connected mode. Any configuration you set this way will be overridden by the configuration set in the Mendix on Kubernetes section of the Mendix Portal.{{% /alert %}} - -Open an environment's `MendixApp` CR [for editing](/developerportal/deploy/private-cloud-operator/#edit-cr) and set the `mode` attribute to `native`: - -```yaml -apiVersion: privatecloud.mendix.com/v1alpha1 -kind: MendixApp -metadata: - name: example-mendixapp -spec: - # Existing configuration - # ... - # Metrics configuration - runtimeMetricsConfiguration: - # Set mode to native - mode: native - # Optional: set the scrape interval - interval: "PT1M" - # Optional: set the agent config - mxAgentConfig: |- - { - … - } - # Optional: set the agent instrumentation config - mxAgentInstrumentationConfig: |- - { - … - } - # … -``` - -If your Prometheus setup is using a custom scrape interval, specify the interval in the `interval` attribute in ISO 8601 Duration format (for example, 'PT1M'). - -If you would like to collect additional metrics, specify a non-empty configuration for `mxAgentConfig`, see [Configuring the Java Instrumentation Agent](#configuring-mxagent),below, for more details. - -Save and apply the changes. - #### Configuring the Java Instrumentation Agent{#configuring-mxagent} By specifying a value for `mxAgentConfig`, you can enable the Mendix [Java instrumentation agent](https://github.com/mendix/mx-agent) and collect additional metrics such as the execution times of microflows, OData/SOAP/REST endpoints, and client activity. diff --git a/content/en/docs/deployment/private-cloud/private-cloud-operator.md b/content/en/docs/deployment/private-cloud/private-cloud-operator.md index 73b14d43b27..e8ce8680f67 100644 --- a/content/en/docs/deployment/private-cloud/private-cloud-operator.md +++ b/content/en/docs/deployment/private-cloud/private-cloud-operator.md @@ -10,9 +10,9 @@ weight: 30 Once you have the Mendix Operator installed in a namespace of your Red Hat OpenShift, or other Kubernetes cluster (see [Creating a Mendix on Kubernetes Cluster](/developerportal/deploy/private-cloud-cluster/)), you can use it to control the deployment of your Mendix app using Mendix Custom Resources (CRs). The Mendix operator then creates the app container and builds the app inside the namespace, together with all the resources the app needs. -This document explains how to provide the CRs through the console or command line for a standalone cluster. This enables you to automate your deployment processes and perform deployments from behind a firewall which would prevent access to the Mendix Portal. +This document explains how to provide the CRs through the console or command line. This enables you to automate your deployment processes and perform deployments from behind a firewall which would prevent access to the Mendix Portal. -Alternatively, you can create a connected cluster and use the Mendix Portal to deploy the app, as described in [Deploying a Mendix App to a Mendix on Kubernetes Cluster](/developerportal/deploy/private-cloud-deploy/). +Alternatively, you can use the Mendix Portal to deploy the app, as described in [Deploying a Mendix App to a Mendix on Kubernetes Cluster](/developerportal/deploy/private-cloud-deploy/). ## Prerequisites for Deploying a Mendix App @@ -211,7 +211,7 @@ You must make the following changes: {{% alert color="warning" %}}Your app can only be deployed to a production environment if [security in the app is set on](/refguide/app-security/). {{% /alert %}} - If you have an offline Runtime license, for example for a standalone cluster, you can configure it by adding a **runtimeLicense** section within the **runtime** section and setting **LicenseId** and **LicenseKey** to the values received from Mendix Support: + If you have an offline Runtime license, you can configure it by adding a **runtimeLicense** section within the **runtime** section and setting **LicenseId** and **LicenseKey** to the values received from Mendix Support: ```yaml apiVersion: privatecloud.mendix.com/v1alpha1 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 f4310608221..434abba961f 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 @@ -371,12 +371,6 @@ The following configuration options are available in OpenShift: * Provide the name of an existing TLS certificate secret to use instead of the default router certificate * Provide a custom domain name (for example, mendix.example.com) to use instead of the default OpenShift route domain -It is also possible to provide a custom TLS configuration for individual environments, overriding the default configuration (only available in **Standalone** Mendix Operator installations): - -* Turn TLS on and off -* Specify the name of an existing TLS certificate secret to use -* Provide the TLS Certificate and Private Key values directly in the environment specification - ### Ingress Mendix on Kubernetes is compatible with the following ingress controllers: @@ -404,12 +398,6 @@ For example, if the domain name is set to mendix.example.com, then apps will hav The DNS server should be configured to route all subdomains (the `*` subdomain, for example, `*.mendix.example.com`) to the ingress/load balancer. -It is also possible to provide a custom TLS configuration for individual environments, overriding the default configuration (only available in **Standalone** Mendix Operator installations): - -* Turn TLS on and off -* Specify the name of an existing TLS certificate secret to use -* Provide the TLS Certificate and Private Key values directly in the environment specification - There are multiple ways of managing TLS certificates: * The Ingress controller can have a default certificate with a wildcard domain (for example, `*.mendix.example.com`). For Ingress controllers which support for [Let's Encrypt](https://letsencrypt.org/), the Ingress controller can also request and manage TLS certificates automatically.