Merge pull request mendix#9138 from Nidhi251289/Portunus_v7_10_0

Global Operator GA Release

Author: katarzyna-koltun-mx

content/en/docs/deployment/private-cloud/private-cloud-cluster/private-cloud-global-operator.md

@@ -1,15 +1,11 @@
 ---
 title: "Running the Mendix Operator in Global Mode"
 url: /developerportal/deploy/global-operator/
-description: "Describes the processes of installing and configuring the Mendix Operator in the Private Cloud in Global mode"
+description: "Describes the processes of installing and configuring the Mendix Operator in the Private Cloud in Global Mode"
 weight: 30
 beta: true
 ---
 
-{{% alert color="info" %}}
-This feature is currently in beta. For more information, see [Beta Releases](/releasenotes/beta-features/).
-{{% /alert %}}
-
 ## Introduction
 
 When running the Mendix Operator in Global mode, one installation of the Mendix Operator and Agent is sufficient to manage applications across multiple namespaces. This Operator mode is recommended for new customers, or customers that want to streamline and simplify their deployments and operations. For existing customers, and for use cases that require having a separate Operator instance for every namespace, the [Standard mode](/developerportal/deploy/standard-operator/) is still available and supported.
@@ -40,7 +36,7 @@ To install and configure the Global Operator, perform the following steps:
 
 4. After the Global Operator cluster is created, click **Add Global Operator Main Namespace**.
 
-    {{% alert color="warning" %}}Ensure that you do not use a namespace that is intended to be a managed namespace, that is, a namespace where you plan to deploy a Mendix app. The Global Operator namespace must be separate from managed namespaces, otherwise you may encounter unexpected results.{{% /alert %}}
+    {{% alert color="warning" %}}Ensure that you do not use a namespace that is intended to be a managed namespace, that is, a namespace where you plan to deploy a Mendix app. The Global Operator main namespace must be separate from managed namespaces, otherwise you may encounter unexpected results.{{% /alert %}}
 
     {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator4.png" class="no-border" >}}
 
@@ -56,6 +52,8 @@ To install and configure the Global Operator, perform the following steps:
 
     {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator6.png" class="no-border" >}}
 
+    4. You can apply the custom TLS and proxy settings in the Global Operator main namespace by just selecting only the **Custom TLS** and **Proxy** options in the Configuration Tool.
+
 7. Verify that the installation was successful by using the following command: 
 
     ```shell
@@ -68,57 +66,64 @@ To install and configure the Global Operator, perform the following steps:
     kubectl -n {globalOperatorNamespace} get pods
     ```
 
-9. In the Private Cloud Portal, verify that the status of the Global Operator namespace is *Connected*, as in the following figure:
+9. In the Private Cloud Portal, verify that the status of the Global Operator main namespace is *Connected*, as in the following figure:
 
     {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator7.png" class="no-border" >}}
 
 10. Click **Namespaces** to go to the **Namespaces Overview** page.
 
     {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator8.png" >}}
 
-11. Install the managed namespace under the Global Operator namespace by clicking **Add Managed Namespace**.
+11. Once the Global Operator main namespace is connected, the **Convert Namespace** and **Add Managed Namespace** buttons are enabled and you can install the managed namespace under the Global Operator namespace by clicking **Add Managed Namespace**.
 
     {{< figure src="/attachments/deployment/private-cloud/global-operator/global-operator9.png" class="no-border" >}}
 
-    {{% alert color="warning" %}}Ensure that you use the same name for the managed namespace in the Portal and in the cluster. Using different names may result in unwanted issues.{{% /alert %}}
+    {{% alert color="warning" %}}Ensure that you use the same name for the managed namespace in the Portal and in the cluster while running the command. Using different names may result in unwanted issues.{{% /alert %}}
 
-12. Open the managed namespace and click **Done**.
+12. Provide the managed namespace name under which you want to deploy the mendix application and click **Done**. 
 
-13. [Configure the namespace](/developerportal/deploy/standard-operator/#configure-namespace).
+    {{% alert color="warning" %}}Ensure that you do not use the name of a main namespace {{% /alert %}}
 
-14. On the **Configuration** page, select the **Operating system** and run the **Configuration** command under the **Configuration** section.
+13. On the **Configuration** page, select the **Operating system** and run the **Configuration** command under the **Configuration** section.
 
-    {{% alert color="warning" %}}Ensure that you do not use a namespace that is already used as a Global Operator namespace. The Global Operator namespace must be separate from managed namespaces, otherwise you may encounter unexpected results.{{% /alert %}}
+    {{% alert color="warning" %}}Ensure that you do not use a namespace that is already used as a Global Operator main namespace. The Global Operator namespace must be separate from managed namespaces, otherwise you may encounter unexpected results.{{% /alert %}}
 
-15. Click **Configure Namespace** and select the items which you want to configure.
-16. In the **Global Operator** section, enter the **Global Operator namespace name**.
-
-    {{% alert color="warning" %}}Ensure that you do not use the name of a managed namespace (that is, a namespace where you plan to deploy a Mendix app).{{% /alert %}}
-
-17. [Configure any remaining namespace settings](/developerportal/deploy/standard-operator/#configure-namespace) and apply the configuration.
+14. Click **Configure Namespace**. Under **Global Operator** section in the cli, provide the main namespace name and select the resources which need to be configured in the managed namespace. Follow [Configure the namespace](/developerportal/deploy/standard-operator/#configure-namespace) for more information. Once the information is provided, under **Review and Apply** section, click **Apply Configuration** 
 
 ### Results
 
 After you configure the managed namespace, the Agent and Operator pod are restarted automatically, so that the Global Operator namespace can process the newly added managed namespace. The managed namespace is added to the Operator configuration for the Global Operator namespace, and the required storage plans are created in the managed namespace.
 
-The Operator configuration for the managed namespace is created as well. The configuration changes inside the managed namespace will take precedence over the global configuration.
+The Operator configuration for the managed namespace is created as well. 
+
+{{% alert color="info" %}}The configuration changes inside the managed namespace will take precedence over the global configuration.{{% /alert %}}
 
 After configuration, the status of managed namespace changes to **Configured**.
 
-Once the managed namespace is configured, you can find the list with all the namespaces managed by the globally installed operator in **Addition Information** section of Global Operator Namespace.
+Once the managed namespace is configured, you can find the list with all the namespaces managed by the globally installed operator in **Additional Information** section of the main namespace. The list is displayed in the **Global Installation Managed Namespaces** section.
 
 {{% alert color="info" %}}
-If the managed namespaces are deleted from the portal, the namespaces will not be deleted from the cluster. The managed namespaces needs to be manually deleted from the cluster. Additionally, you also need to remove the managed namespace from the list of managed namespaces in the Operator configuration of the main namespace.
+If you delete the managed namespaces from the portal, they are not deleted from the cluster. You must delete them from the cluster manually. You must also remove the managed namespace from the list of managed namespaces in the Operator configuration of the main namespace.
+
+The main namespace cannot be deleted from the portal until the managed namespaces are deleted from the cluster.
 {{% /alert %}}
 
 ### Next Steps
 
-After everything is configured, you can deploy the application. For more information, see [Deploy Application](/developerportal/deploy/private-cloud-deploy/).
+After everything is configured, you can deploy the application. For more information, see [Deploy Application](/developerportal/deploy/private-cloud-deploy/). The application is deployed within the managed namespace.
 
 ## Convert Namespace from Standard to Global Operator {#convert-standard-operator-to-global-operator}
 
 You can convert a namespace which currently uses the standard operator to be a Global Operator managed namespace by completing the following steps.
 
+{{% alert color="info" %}}
+Ensure that the namespace to be converted is in the same cluster as the main namespace. Additionally, ensure that both namespaces have the same operator version; otherwise, the conversion will not be performed.
+{{% /alert %}}
+
+{{% alert color="info" %}}
+Currently, there is no API support to convert a namespace from standard to global operator.
+{{% /alert %}}
+
 1. On the Cluster Overview page, click **Convert Namespace**.
 
    {{< figure src="/attachments/deployment/private-cloud/global-operator/convert-namespace.png" >}}
@@ -131,7 +136,7 @@ You can convert a namespace which currently uses the standard operator to be a G
 
     {{< figure src="/attachments/deployment/private-cloud/global-operator/convert-namespace-command.png" >}}
 
-4. Run the command.
+4. Run the command and make sure that you are logged in to the cluster where the conversion must be done.
 
     Once the command has been run successfully, your namespace will be converted to managed namespace as part of Global Operator installation on the cluster side.
 
@@ -141,8 +146,10 @@ You can convert a namespace which currently uses the standard operator to be a G
 
 5. Once the conversion command runs successfully, click **Next** to be redirected to the Conversion Summary pop-up page, which will confirm the successful conversion. This step will also ensure that the namespace conversion is visible on the portal side as well.
 
+6. Click **Done** to return to the Namespaces Overview page.
+
 {{% alert color="info" %}}
-Once all the standard namespaces within a cluster created on portal side are converted to Global Operator Managed namespace, then the status of the cluster would be changed to **Conversion Finalized**, otherwise it will show **Conversion in Progress** if not all the namespaces within that cluster are converted.
+After the standard namespaces are converted to Global Operator Managed namespace, the status of the cluster in which the standard namespace was present before conversion is changed to **Conversion Finalized**. If not all the namespaces within the cluster are converted yet, the status shows **Conversion in Progress**.
 {{% /alert %}}
 
 ## Licensing
@@ -152,11 +159,11 @@ Once all the standard namespaces within a cluster created on portal side are con
 Configure Private Cloud License Management (PCLM) in the Global Operator namespace. For more information, see [Private Cloud License Manager](/developerportal/deploy/private-cloud/private-cloud-license-manager/).
 
 {{% alert color="info" %}}
-For Global Operator installations, execute the above command in both the Global Operator namespace and its managed namespaces where the license is intended to be applied. Make sure that identical PCLM license details are configured for both the Managed and Global Operator namespaces to avoid unexpected outcomes.
+For Global Operator installations, execute the commands from the PCLM section in both the Global Operator namespace and its managed namespaces where the license must be applied. Make sure that identical PCLM license details are configured for both the Managed and Global Operator namespaces to avoid unexpected outcomes.
 {{% /alert %}}
 
 {{% alert color="warning" %}}
-It is crucial to maintain consistent Operator configuration for PCLM in both the Global Operator and managed namespaces. This requires uniformity in server URLs and credential secret names used both in managed and Global Operator namespaces. Any deviations from this practice may lead to unexpected and undesired outcomes.
+It is crucial to maintain consistent Operator configuration for PCLM in both the Global Operator main namespace and managed namespaces. This requires uniformity in server URLs and credential secret names used both in managed and Global Operator namespaces. Any deviations from this practice may lead to unexpected and undesired outcomes.
 {{% /alert %}}
 
 Licenses imported in the PCLM Server appear in the PCLM Statistics section of the Global Operator main namespace. You can see both **Runtime** and **Operator** license.
@@ -165,4 +172,4 @@ Claimed licenses are visible in the PCLM Statistics section of the Managed names
 
 ## Upgrading Managed Namespaces
 
-Currently, the upgrade procedure is not available for managed namespaces.
+When you [upgrade](/developerportal/deploy/private-cloud-upgrade-guide/#upgrade-cluster) the Global Operator main namespace, the managed namespaces within the global operator namespace are also automatically upgraded.

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

@@ -12,6 +12,12 @@ For information on the current status of deployment to Mendix for Private Cloud
 
 ## 2025
 
+### March 6, 2025
+
+#### General Availability Release
+
+* We have released the general availability (GA) version of Global Operator in the Private Cloud.
+
 ### February 19, 2025
 
 #### Mendix Operator v2.21.0 {#2.21.0}