Merge branch 'latest' into W-14938259-permissions-rtf-runtime-manager-kt

kevintroller · web-flow · commit 21ba9f0ba7ba · 2025-01-17T15:11:32.000-03:00
diff --git a/.vscode/settings.json b/.vscode/settings.json
@@ -12,8 +12,9 @@
         "**/.exchange.xml": true,
         "**/.vscode": true,
         "**/.mvn": true,
+        "**/.tmp": true,
+        "**/.settings": true,
         "**/.exchange_modules_tmp": true,
         ".mule": true
-    },
-    "asciidoc.antora.enableAntoraSupport": false
+    }
 }
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -1 +1 @@
-* @sarathecoubian @mulesoft/team-docs
+* @luanamulesoft @kevintroller @mulesoft/team-docs
diff --git a/cloudhub-2/modules/ROOT/pages/_partials/caveats.adoc b/cloudhub-2/modules/ROOT/pages/_partials/caveats.adoc
@@ -11,6 +11,10 @@ You cannot change the name of an app after you deploy it. To change the name, yo
 // end::noRenameApp[]
 
 //tag::supportedMule[]
-CloudHub 2.0 supports Mule runtime engine versions 4.3.x, 4.4.x, 4.5.x.
+CloudHub 2.0 supports Mule runtime engine versions 4.3.x and later.
 Mule 3.x is not supported.
 // end::supportedMule[]
+
+//tag::softDelete[]
+Runtime Manager doesn't support deploying an application to CloudHub 2.0 or Runtime Fabric if the asset was previously xref:exchange::to-delete-asset.adoc[soft-deleted] in Exchange.
+// end::softDelete[]
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-architecture.adoc b/cloudhub-2/modules/ROOT/pages/ch2-architecture.adoc
@@ -138,7 +138,7 @@ The following table summarizes what DNS records are available for your applicati
 [%header,cols="15a,10a,30a,40a,40a"]
 |===
 | Region Name | Region | Target ID | Example DNS Record | Target Name
-5+h| US Runtime Plane Regions
+5+h| US Cloud: Runtime Plane Regions
 | US East (N. Virginia) |usa-e1 | `cloudhub-us-east-1` | `myapp-_uniq-id_._shard_.usa-e1.cloudhub.io` | `Cloudhub-US-East-1`
 | US East (Ohio) |usa-e2| `cloudhub-us-east-2` | `myapp-_uniq-id_._shard_.usa-e2.cloudhub.io` | `Cloudhub-US-East-2`
 | US West (N. California) |usa-w1 |`cloudhub-us-west-1` | `myapp-_uniq-id_._shard_.usa-w1.cloudhub.io` | `Cloudhub-US-West-1`
@@ -151,11 +151,13 @@ The following table summarizes what DNS records are available for your applicati
 | EU (Ireland) |irl-e1 | `cloudhub-eu-west-1` | `myapp-_uniq-id_._shard_.irl-e1.cloudhub.io` | `Cloudhub-EU-West-1`
 | EU (Frankfurt) |deu-c1 | `cloudhub-eu-central-1` | `myapp-_uniq-id_._shard_.deu-c1.cloudhub.io` | `Cloudhub-EU-Central-1`
 | EU (London) |gbr-e1 | `cloudhub-eu-west-2` | `myapp-_uniq-id_._shard_.gbr-e1.cloudhub.io` | `Cloudhub-EU-West-2`
-5+h|MuleSoft Government Cloud Region
-| US Gov West |usag-w1.gov| N/A | `myapp-_uniq-id_._shard_.usg-w1.gov.cloudhub.io` | N/A
-5+h| EU Runtime Plane Regions
+5+h| EU Cloud: Runtime Plane Regions
 | EU (Ireland) |irl-e1.eu1 | `cloudhub-eu-west-1` | `myapp-_uniq-id_._shard_.irl-e1.eu1.cloudhub.io` | `Cloudhub-EU-West-1`
 | EU (Frankfurt) |deu-c1.eu1 | `cloudhub-eu-central-1` | `myapp-_uniq-id_._shard_.deu-c1.eu1.cloudhub.io` | `Cloudhub-EU-Central-1`
+5+h| Canada Cloud: Runtime Plane Regions
+| Canada (Central) |can-c1| `cloudhub-ca-central-1` | `myapp-uniq-id.can-c1.ca1.cloudhub.io` | `Cloudhub-CA-Central-1`
+5+h| Japan Cloud: Runtime Plane Regions
+| Asia Pacific (Tokyo) |jpn-e1| `cloudhub-ap-northeast-1` | `myapp-uniq-id.jpn-e1.jp1.cloudhub.io` | `Cloudhub-AP-Northeast-1`
 |===
 
 For example, if you deploy an application named `myapp` to Canada (Central), the domain used to access the application is `myapp-_uniq-id_._shard_.can-c1.cloudhub.io`.
@@ -258,7 +260,7 @@ The monitoring script exits and the application is left unchanged until you manu
 ////
 
 The logs report the details of the restart procedure.
-You can also receive alerts and diagnostic information if your application becomes unresponsive.
+You can also receive alerts and diagnostic information if your application becomes unresponsive. For more information, see xref:ch2-config-app-alerts.adoc[].
 
 
 == Security
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-clustering.adoc b/cloudhub-2/modules/ROOT/pages/ch2-clustering.adoc
@@ -47,6 +47,8 @@ If the entire application is updated or redeploying while the batch is running,
 The main solution for persistent batch jobs in CloudHub 2.0 is to use 
 xref:object-store::index.adoc[].
 
+In Kubernetes, a Horizontal Pod Autoscaler (HPA) automatically updates a workload resource to scale the workload to match demand. Horizontal scaling automatically deploys more pods as a response to an increased load. As a result of these regular autoscaling operations, an application can be changed to a new replica without user action.
+
 == Enable Clustering Features
 
 You can enable and disable either or both features of clustering in one of two ways:
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-comparison.adoc b/cloudhub-2/modules/ROOT/pages/ch2-comparison.adoc
@@ -50,7 +50,7 @@ CloudHub 2.0 does not support the following infrastructure features or functions
 
 CloudHub 2.0 application behavior deviates from CloudHub 1.0 in the following ways:
 
-* Only Mule 4.3.0 through 4.6.x are supported.
+* Only Mule 4.3.0 and later versions are supported.
 * Application bursting depends on the resource usage of other applications that are deployed in the private space and is not guaranteed.
 * Secure application properties are stored in encrypted, private vaults and cannot be viewed directly by users or MuleSoft staff after they are created. Secure properties are accessible only by the application itself. You can overwrite the properties to new values at any time.
 * Use xref:mq::index.adoc[Anypoint MQ] for persistent queues and other queue management. Persistent queues are not supported.
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-config-app-alerts.adoc b/cloudhub-2/modules/ROOT/pages/ch2-config-app-alerts.adoc
@@ -17,19 +17,13 @@ This limit is enforced by a combination of organization, environment, alert (nam
 [[configure-custom-app-alerts]]
 == Create a Custom Alert
 
-Use Runtime Manager to set up an alert related to successful app deployment:
-
-// SELECT APPS SHARED
-include::partial$select-private-space.adoc[tag=selectAppsPage]
-include::partial$select-private-space.adoc[tag=clickAppName]
-. In the navigation menu, click *Alerts*.
-. On the *Alerts* page, click the blue plus icon (*+*).
-. On the *Create an Alert* page, configure your custom alert and click *Submit*:
-// +
-// <screenshot>
-// +
-// image::alerts-custom-rtm-create.png[Applications field in the Create an Alert window]
-+
+In Runtime Manager, bind the custom notification to an alert:
+
+. From Anypoint Platform, select *Runtime Manager*.
+. In the navigation menu, click *Alerts*.
+. Click the blue plus icon (*+*) to create a new alert.
+. In the *Create an Alert* page, configure your custom alert and click *Submit*:
+
 Name::
 Enter a meaningful name for the custom alert.
 Severity level::
@@ -40,9 +34,9 @@ Select the severity level to apply to the alert:
 Source::
 Select *Applications* for the alert source.
 Application type::
-Select *CloudHub Applications*.
+Select *CloudHub 2.0 and RTF Applications*.
 Applications::
-Select the application that contains the flow that you configured to trigger a custom notification.
+Select the application that contains the flow that you configured to trigger a custom alert.
 Condition::
 Select one of the following:
 ** Deployment success: An app deploys and runs
@@ -58,6 +52,8 @@ Enter the email addresses for notification recipients.
 You can use variables in the alert *Subject* and *Message* fields.
 For information about using variables in alerts, see xref:runtime-manager::alerts-on-runtime-manager.adoc#alert-variables[Alert Variables].
 
+When you trigger the alert, the specified recipients receive an email with the custom message you added to the app.
+
 == See Also
 
 * xref:monitoring::basic-alerts.adoc[]
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-config-endpoints-paths.adoc b/cloudhub-2/modules/ROOT/pages/ch2-config-endpoints-paths.adoc
@@ -140,6 +140,9 @@ http://helloch2:8081/hello
 ```
 If required, replace `http` with `https`.
 
+[NOTE]
+You can't send traffic between applications in different namespaces by using `svc.cluster.local` endpoints.
+
 === Application-to-Application Communication
 
 An application communicates with another application via:
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-deploy-api.adoc b/cloudhub-2/modules/ROOT/pages/ch2-deploy-api.adoc
@@ -26,7 +26,7 @@ GET
 https:/anypoint.mulesoft.com/runtimefabric/api/organizations/{organizationId}/privatespaces/{privatespaceId}/ports?available=true&count=10
 ----
 
-In the request, the `available` parameter enables you to alternate between used and unused ports.
+In the request, the `available` parameter provides unused ports in the response.
 The `count` parameter lets you specify the number of ports, between 1 and 10. The actual availability of ports limits the end result.
 
 Response: 
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-deploy-private-space.adoc b/cloudhub-2/modules/ROOT/pages/ch2-deploy-private-space.adoc
@@ -5,6 +5,10 @@ You deploy apps to a private space using Runtime Manager.
 [IMPORTANT]
 include::partial$caveats.adoc[tag=supportedMule]
 
+[NOTE]
+include::partial$caveats.adoc[tag=softDelete]
+
+
 [[deploy-app-private-space]]
 == Deploy an App to a Private Space
 
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-deploy-shared-space.adoc b/cloudhub-2/modules/ROOT/pages/ch2-deploy-shared-space.adoc
@@ -5,6 +5,9 @@ You deploy apps to a shared space using Runtime Manager.
 [IMPORTANT]
 include::partial$caveats.adoc[tag=supportedMule]
 
+[NOTE]
+include::partial$caveats.adoc[tag=softDelete]
+
 == Deploy an App to a Shared Space
 
 //SELECT APP SHARED
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-limits.adoc b/cloudhub-2/modules/ROOT/pages/ch2-limits.adoc
@@ -14,9 +14,9 @@ Transit gateway connections:: 5 per private space, depending on available networ
 
 HTTP header length (`maxHeaderLength`):: 32K
 
-Firewall rules (inbound):: 180
+Firewall rules (inbound):: 300
 
-Firewall rules (outbound):: 180
+Firewall rules (outbound):: 300
 
 Application size:: Up to 350 MB
 
@@ -40,7 +40,7 @@ Ingress controller `content-length` in POST requests:: 0 or greater. `content-le
 
 Anypoint Platform CloudHub 2.0 API rate limit:: 15 requests per second per remote IP address.
 
-
+For information about limits in Exchange, see xref:exchange::asset-versions.adoc#asset-limits[Asset Limits].
 
 
 [NOTE]
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-manage-schedules.adoc b/cloudhub-2/modules/ROOT/pages/ch2-manage-schedules.adoc
@@ -46,6 +46,7 @@ Use the *Schedules* tab or the CloudHub 2.0 API to manage CloudHub 2.0 schedules
 ** If the value is a placeholder (such as `${cronExpression}`) that is provided at the time of deployment, the exact value of the placeholder does not appear in the user interface.
 ** CloudHub 2.0 uses a default value of `60000`.
 * If you make changes to schedulers, you should reupload the application to Exchange to ensure the expected scheduler behavior occurs.
+* CloudHub 2.0 schedules run concurrently by default. The Scheduler triggers the execution of a schedule flow while a previously-triggered execution is still running. To run schedules sequentially, set the `disallowConcurrentExecution` property as `true` in the xref:mule-runtime::scheduler-concept.adoc#props_scheduler[scheduler] configuration file. 
 
 == Before You Begin
 
diff --git a/cloudhub-2/modules/ROOT/pages/ch2-patch-updates.adoc b/cloudhub-2/modules/ROOT/pages/ch2-patch-updates.adoc
@@ -119,18 +119,7 @@ include::release-notes::partial$mule-runtime/mule-lts-edge-release-cadence.adoc[
 
 The following table shows the Mule runtime release cadence support for CloudHub 2.0:
 
-[%header%autowidth.spread]
-|===
-|Mule Version| Release Date |Java Version | End of Standard Support | End of Extended Support
-|4.5 Edge | October 2023 |8 | February 2024 | June 2024
-|4.6 LTS | February 2024 | 8 and 17 | February 2025 | February 2026
-|4.6 Edge | February 2024 |8 and 17| June 2024 | October 2024
-|4.7 Edge | June 2024 | 8 and 17 | October 2024 | February 2025
-|4.8 Edge | October 2024 | 8 and 17 | February 2025 | June 2025
-|4.9 LTS | February 2025 | 17 | February 2026 | February 2027
-|4.9 Edge | February 2025 | 17 | June 2025 | October 2025
-|===
-
+include::release-notes::partial$mule-runtime/mule-lts-edge-release-cadence.adoc[tags=MuleIntro1A2]
 
 [NOTE]
 If you are a CloudHub or a CloudHub 2.0 customer and you want to create or test Mule 4.6 applications in Anypoint Studio, the Studio version required is the next upcoming release in March. Meanwhile, MuleSoft enables you to deploy new apps in Mule runtime 4.5e version via API, Mule Maven plugin, and Anypoint Platform CLI starting February 14 until April 19. Auto-upgrade from Mule 4.5 Edge to Mule 4.6 Edge for CloudHub and CloudHub 2.0 applications will be performed in April instead of February. See https://help.mulesoft.com/s/article/Mule-Runtime-4-6-release-temporary-changes-to-auto-upgrade-and-new-app-deployment[Temporary changes to auto-upgrade and new app deployment for Mule 4.5 Edge].
@@ -206,7 +195,7 @@ image::ch2-app-edge-auto-update.png[Banner indicating the date of automatic upda
 [[ps-status]]
 == Possible Status Types for Private Space Upgrades and Updates
 
-The *Update Available* column in the *Private Space* page shows the status of infrastructure upgrades and runtime updates for your private space.
+The *Infra Status* column in the *Private Space* page shows the status of infrastructure upgrades for your private space.
 
 [%header,cols="20,70"]
 |===
@@ -218,6 +207,8 @@ The *Update Available* column in the *Private Space* page shows the status of in
 |Upgrading |The private space is undergoing an infrastructure upgrade, either scheduled, self-triggered, or as part of a monthly infrastructure upgrade. 
 |Updating |The private space is undergoing an update that was triggered by a configuration change. 
 |Failed |The private space experienced a failure which can be related to a user configuration update, or to an infrastructure upgrade, either scheduled, self-triggered, or as part of a monthly infrastructure upgrade. 
+|Degraded |The private space is in degraded state.
+| -- |Unable to get the details of the private space status and the status is unknown.
 |===
 
 == Security Updates
diff --git a/cloudhub-2/modules/ROOT/pages/index.adoc b/cloudhub-2/modules/ROOT/pages/index.adoc
@@ -14,6 +14,13 @@ CloudHub 2.0:
 
 For CloudHub 2.0 pricing information, contact either your account executive or your account development representative.
 
+[[cloudhub2-hyperforce]]
+== CloudHub 2.0 on Hyperforce
+
+All features of CloudHub 2.0 are supported on Hyperforce with these exceptions:
+
+When deploying to any Hyperforce supported regions, deleting the default egress traffic route, `0.0.0.0`, can result in Anypoint Monitoring to not work in CloudHub 2.0.
+
 
 == See Also
 
diff --git a/cloudhub-2/modules/ROOT/pages/ps-config-app-level-egress.adoc b/cloudhub-2/modules/ROOT/pages/ps-config-app-level-egress.adoc
@@ -130,21 +130,37 @@ If you enable egress for a domain that includes redirection, such as when `sales
 Wildcard records are not supported. For example, `salesforce.com` does not automatically cover `example.salesforce.com`. 
 
 [NOTE]
+====
 You can't enable domains with double hyphens. For example, `abc--xyz.com`.  
 
+Domains with identical IP addresses are handled together. Allowing one domain allows all identical domains.
+====
+
 == Configure an Application-Level Egress Connection to API Manager
 
 To add application-level egress support to API Manager, add a custom rule group with the following rule to allow egress to the Anypoint control plane:
 
 * *Protocol*: `HTTPS`
 * *Destination*: `Custom Domains`
 ** With value:
-*** For prod: `anypoint.mulesoft.com`
-*** For prod-eu: `eu1.anypoint.mulesoft.com`
+*** For prod: 
+**** `anypoint.mulesoft.com`
+**** `exchange-files.anypoint.mulesoft.com`
+**** `analytics-ingest.anypoint.mulesoft.com`
+*** For prod-eu: 
+**** `eu1.anypoint.mulesoft.com`
+**** `exchange-files.eu1.anypoint.mulesoft.com`
+**** `analytics-ingest.eu1.anypoint.mulesoft.com`
+
+Depending on your use case, add Anypoint Platform hostnames and ports for your application to communicate with the online Anypoint Platform APIs and services that are managed by MuleSoft. See xref:mule-gateway::mule-gateway-hostnames.adoc[].
 
 [NOTE]
+====
 When configuring application-level egress connections to Anypoint MQ, Object Store v2, or API Manager, you must also allow outbound access to all 443 ports at the private-space level separately. For more information about allowing outbound access to 443 ports, visit xref:ps-config-fw-rules.adoc[]. 
 
+You can't use custom domains with private space internal DNS.
+====
+
 == Performance Impact
 
 Given the extra layer of validation, using the application-level egress rules can introduce three-millisecond to ten-millisecond network latency delays to your applications' connections. To balance security and performance:
diff --git a/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc b/cloudhub-2/modules/ROOT/pages/ps-config-domains.adoc
@@ -73,6 +73,17 @@ _Private DNS targets_ can only be reached from inside a private network, or thro
 
 When you add the TLS context, you can select the ciphers to use with the TLS context.
 
+[NOTE]
+====
+CloudHub 2.0 private space ingress support for TLS cipher version 1.1 ends starting January 31, 2025. Don’t use the following TLS 1.1 ciphers after that date:
+```
+TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
+TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
+TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
+TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
+```
+====
+
 
 [[before-you-begin]]
 == Before You Begin
@@ -284,6 +295,7 @@ ciphers.
 ** Click *Select a cipher to add* to choose a different cipher.
 . Click *Update TLS Context* or *Cancel* to discard changes.
 
+Add the LetsEncrypt root to your truststore if you want the client to trust the `cloudhub.io` certificates.
 
 == See Also
 
diff --git a/cloudhub-2/modules/ROOT/pages/ps-create-configure.adoc b/cloudhub-2/modules/ROOT/pages/ps-create-configure.adoc
@@ -66,6 +66,9 @@ After you configure internal DNS, the *Network* tab indicates the number of conf
 
 image::internal-dns.png[Internal DNS configuration in the Private Network section]
 
+[NOTE]
+You can't add MuleSoft domains or public domains as private space internal DNS.
+
 [[create-connection-to-external-network]]
 == Create a Connection to an External Network
 
@@ -92,4 +95,3 @@ Depending on the connection type you selected:
 * xref:ps-create-configure-tgw.adoc[]
 * xref:ps-configure.adoc[]
 * xref:ps-manage.adoc[]
-
diff --git a/cloudhub-2/modules/ROOT/pages/ps-gather-setup-info.adoc b/cloudhub-2/modules/ROOT/pages/ps-gather-setup-info.adoc
@@ -251,6 +251,8 @@ The following internal private DNS domains are not supported:
 * `internal`
 * `local/domain.com`
 
+You can't add MuleSoft domains or public domains as private space internal DNS.
+
 // To specify an internal domain, use the second-level domain name, such as `mulesoft.com`.
 
 [NOTE]
diff --git a/hosting-home/modules/ROOT/pages/index.adoc b/hosting-home/modules/ROOT/pages/index.adoc
diff --git a/hyperforce/antora.yml b/hyperforce/antora.yml
diff --git a/hyperforce/modules/ROOT/_attributes.adoc b/hyperforce/modules/ROOT/_attributes.adoc
diff --git a/hyperforce/modules/ROOT/nav.adoc b/hyperforce/modules/ROOT/nav.adoc
diff --git a/hyperforce/modules/ROOT/pages/configure-mule-hyperforce.adoc b/hyperforce/modules/ROOT/pages/configure-mule-hyperforce.adoc
diff --git a/hyperforce/modules/ROOT/pages/deploy-mule-apps-hyperforce.adoc b/hyperforce/modules/ROOT/pages/deploy-mule-apps-hyperforce.adoc
diff --git a/hyperforce/modules/ROOT/pages/hyperforce-release-notes.adoc b/hyperforce/modules/ROOT/pages/hyperforce-release-notes.adoc
diff --git a/hyperforce/modules/ROOT/pages/index.adoc b/hyperforce/modules/ROOT/pages/index.adoc

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-* @sarathecoubian @mulesoft/team-docs`
	`1`	`+* @luanamulesoft @kevintroller @mulesoft/team-docs`