Merge branch 'latest' into W-13595035-downtime-CH-deployment-LDS

Author: luanamulesoft

cloudhub/modules/ROOT/assets/image-source-files/tgw-detach-vpc.graffle

@@ -108,7 +108,28 @@ include::release-notes::partial$mule-runtime/mule-lts-edge-release-cadence.adoc[
 
 include::release-notes::partial$mule-runtime/mule-lts-edge-release-cadence.adoc[tags=MuleIntro1]
 
-include::release-notes::partial$mule-runtime/mule-lts-edge-release-cadence.adoc[tags=MuleIntro1A]
+// include::release-notes::partial$mule-runtime/mule-lts-edge-release-cadence.adoc[tags=MuleIntro1A]
+
+== Mule Runtime Release Cadence Support
+
+The following table shows the Mule runtime release cadence support for CloudHub:
+
+[%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
+|===
+
+
+[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].
+
 
 include::release-notes::partial$mule-runtime/mule-lts-edge-release-cadence.adoc[tags=MuleIntro2]
 

cloudhub/modules/ROOT/assets/image-source-files/tgw-route-added.graffle

@@ -220,9 +220,11 @@ image::tgw-add-vpc-route.png[Add VPC route]
 Anypoint Platform submits the new route to AWS.
 
 When the route addition succeeds, the *Transit Gateways* page shows the *Route added* message
-and the *Transit Gateways* page shows the route CIDR in the route table.
+and the *Transit Gateways* page shows the route CIDR in the route tables.
 
-In the route table, added routes show *Transit Gateway* as the value in the *Next Hop* column:
+In the route tables, added routes show *Transit Gateway* as the value in the *Next Hop* column. 
+
+Specific routes attached to the transit gateway show under *Transit Gateway Routes*. Other routes in the VPC show under *VPC Routes*.
 
 image::tgw-route-added.png[Transit Gateway in the Next Hop column of the route table]
 

cloudhub/modules/ROOT/assets/images/tgw-detach-vpc.png

@@ -35,7 +35,9 @@ Anypoint Platform submits the new route to AWS.
 When the route addition succeeds, the *Transit Gateways* page shows the *Route added* message
 and the *Transit Gateways* page shows the route CIDR in the route table.
 
-In the route table, added routes show *Transit Gateway* as the value in the *Next Hop* column:
+In the route tables, added routes show *Transit Gateway* as the value in the *Next Hop* column. 
+
+Specific routes attached to the transit gateway show under *Transit Gateway Routes*. Other routes in the VPC show under *VPC Routes*.
 
 image::tgw-route-added.png[Transit Gateway in the Next Hop column of the route table]