Merge branch 'main' into patch-3

Author: shorejen

docs/10-concepts/abap-development-tools-for-eclipse-54dd712.md

@@ -54,7 +54,7 @@ In particular, ABAP development tools for Eclipse is a modern development toolse
 
 The [ABAP Development Tools for Eclipse Guide](https://help.sap.com/docs/abap-cloud/abap-development-tools-user-guide/about-abap-development-tools-user-guide) describes the following functionalities and usage of ADT ...
 
--   Joule for developers, ABAP AI capabilities supports you in the end-to-end development using generative AI and can be integrated into ABAP development tools for Eclipse. It's currently only available for customers using SAP BTP ABAP environment or SAP S/4HANA Cloud Public Edition. To leverage Joule for developers, ABAP AI capabilities, you need to purchase an additional license. See [Getting Started](https://help.sap.com/docs/abap-ai/generative-ai-in-abap-cloud/prerequisites-and-required-authorizations).
+-   SAP Joule for developers, ABAP AI capabilities supports you in the end-to-end development using generative AI and can be integrated into ABAP development tools for Eclipse. It's currently only available for customers using SAP BTP ABAP environment or SAP S/4HANA Cloud Public Edition. To leverage Joule for developers, ABAP AI capabilities, you need to purchase an additional license. See [Getting Started](https://help.sap.com/docs/abap-ai/generative-ai-in-abap-cloud/prerequisites-and-required-authorizations).
 -   within the ABAP core development scenario. In particular, it focuses on use cases for creating, editing, testing, debugging, and profiling development objects like ABAP classes, ABAP Dictionary objects, function modules, and so on.
 
 -   for Core Data Services \(CDS\) in ABAP development for SAP HANA scenarios. In particular, it focuses on use cases for creating, editing, testing, and analyzing **ABAP CDS entities** like data definitions, and so on.

docs/10-concepts/bringing-your-corporate-identity-provider-for-platform-users-8980b91.md

@@ -55,5 +55,5 @@ In SAP Cloud Identity Services - Identity Authentication in Neo subaccounts, the
 
 [Establish Trust and Federation of Custom Identity Providers for Platform Users](../50-administration-and-ops/establish-trust-and-federation-of-custom-identity-providers-for-platform-users-c368984.md "You want to use a custom identity provider for the platform users of SAP BTP in different environments and at the different account levels: global account, directory, and subaccount. By default, platform users in multi-environment subaccounts are users in the default identity provider.")
 
-[Configure a Custom Identity Provider for Kyma](../60-security/configure-a-custom-identity-provider-for-kyma-67bcc6e.md "Enable the Kyma environment with a custom identity provider (IdP).")
+[Configuring a Custom Identity Provider for Kyma](../60-security/configuring-a-custom-identity-provider-for-kyma-67bcc6e.md "Enable the Kyma environment with a custom identity provider (IdP).")
 

docs/10-concepts/kyma-environment-468c2f3.md

@@ -47,3 +47,5 @@ SAP systems connected to a Kyma environment expose APIs and events. To extend th
 
 [Discovery Center](https://discovery-center.cloud.sap/serviceCatalog/kyma-runtime)
 
+[What's New for SAP Business Technology Platform](https://help.sap.com/whats-new/cf0cb2cb149647329b5d02aa96303f56?version=Cloud)
+

docs/10-concepts/kyma-modules-0dda141.md

@@ -275,7 +275,7 @@ With the Serverless module, you can define simple code snippets \(Functions\) wi
 <td valign="top">
 
 -   [Serverless Module](../30-development/serverless-module-eb84ff5.md)
--   [Serverless Configuration](../30-development/serverless-configuration-4a0ae14.md)
+-   [Configuring Serverless](../30-development/configuring-serverless-b40a119.md)
 -   [Deploy Workloads in the Kyma Environment to Extend SAP Systems](../30-development/deploy-workloads-in-the-kyma-environment-to-extend-sap-systems-fe4ba5b.md)
 -   [GitHub repository: Serverless](https://github.com/kyma-project/serverless-manager)
 

docs/10-concepts/regions-and-api-endpoints-available-for-the-cloud-foundry-environment-f344a57.md

@@ -1127,7 +1127,7 @@ us-east-1
 
 **cf-us10:**
 
-52.200.16.71, 52.23.123.125, 52.202.170.155, 18.210.47.160, 18.211.235.11, 54.156.172.106, 34.234.191.59, 34.192.134.47, 18.204.173.15, 3.213.197.54, 184.73.43.82, 52.20.242.182, 3.216.16.207, 34.225.190.250, 52.2.110.230, 54.234.93.200, 35.153.88.132, 52.204.111.138, 3.88.250.160, 54.221.30.91, 52.71.83.110, 52.200.165.163, 54.208.119.130, 34.202.136.35, 34.192.100.96, 54.85.65.82, 54.205.71.200,18.97.36.224/27
+52.200.16.71, 52.23.123.125, 52.202.170.155, 18.210.47.160, 18.211.235.11, 54.156.172.106, 34.234.191.59, 34.192.134.47, 18.204.173.15, 3.213.197.54, 184.73.43.82, 52.20.242.182, 3.216.16.207, 34.225.190.250, 52.2.110.230, 54.234.93.200, 35.153.88.132, 52.204.111.138, 3.88.250.160, 54.221.30.91, 52.71.83.110, 52.200.165.163, 54.208.119.130, 34.202.136.35, 34.192.100.96, 54.85.65.82, 54.205.71.200,18.97.43.224/27
 
 **cf-us10-001:**
 
@@ -1811,6 +1811,58 @@ cn40.platform.sapcloud.cn
 
 [Open Cockpit](https://cockpit.cn40.platform.sapcloud.cn/cockpit)
 
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+SAP Cloud Infrastructure
+
+</td>
+<td valign="top">
+
+eu01
+
+</td>
+<td valign="top">
+
+Europe \(Frankfurt\) - EU Access Only
+
+</td>
+<td valign="top">
+
+cf-eu01
+
+</td>
+<td valign="top">
+
+eu-de-2
+
+</td>
+<td valign="top">
+
+130.214.199.0/25, 130.214.252.0/25
+
+</td>
+<td valign="top">
+
+130.214.199.128/28, 130.214.252.224/28
+
+</td>
+<td valign="top">
+
+api.cf.eu01.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+eu01.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[Open Cockpit](https://cockpit.btp.cloud.sap/)
+
 </td>
 </tr>
 </table>

docs/10-concepts/regions-and-api-endpoints-for-the-abap-environment-879f373.md

@@ -58,6 +58,53 @@ Cockpit Logon
 <tr>
 <td valign="top">
 
+SAP Cloud Infrastructure
+
+</td>
+<td valign="top">
+
+eu01
+
+</td>
+<td valign="top">
+
+Germany \(Frankfurt\)
+
+</td>
+<td valign="top">
+
+cf-eu01
+
+</td>
+<td valign="top">
+
+eu-de-2
+
+</td>
+<td valign="top">
+
+130.214.190.0/26, 130.214.228.32/27, 130.214.164.0/26
+
+</td>
+<td valign="top">
+
+api.cf.eu01.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+eu01.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[https://eu-access.cockpit.btp.cloud.sap/](https://eu-access.cockpit.btp.cloud.sap/)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
 Amazon Web Services
 
 </td>
@@ -1074,6 +1121,53 @@ Google Cloud
 </td>
 <td valign="top">
 
+il30
+
+</td>
+<td valign="top">
+
+Israel \(Tel Aviv\)
+
+</td>
+<td valign="top">
+
+cf-il30
+
+</td>
+<td valign="top">
+
+me-west1
+
+</td>
+<td valign="top">
+
+34.165.172.174, 34.165.28.224, 34.165.26.44, 34.165.46.220, 34.165.133.5, 34.165.21.8
+
+</td>
+<td valign="top">
+
+api.cf.il30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+il30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[https://emea.cockpit.btp.cloud.sap/](https://emea.cockpit.btp.cloud.sap/)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Google Cloud
+
+</td>
+<td valign="top">
+
 in30
 
 </td>
@@ -1215,6 +1309,100 @@ Google Cloud
 </td>
 <td valign="top">
 
+sa30
+
+</td>
+<td valign="top">
+
+KSA \(Dammam - KSA Regulated Customers\)
+
+</td>
+<td valign="top">
+
+cf-sa30
+
+</td>
+<td valign="top">
+
+me-central2
+
+</td>
+<td valign="top">
+
+34.166.122.101, 34.166.13.193, 34.166.133.79, 34.166.95.100, 34.166.102.25, 34.166.180.181
+
+</td>
+<td valign="top">
+
+api.cf.sa30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+sa30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[https://emea.cockpit.btp.cloud.sap/](https://emea.cockpit.btp.cloud.sap/)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Google Cloud
+
+</td>
+<td valign="top">
+
+sa31
+
+</td>
+<td valign="top">
+
+KSA \(Dammam - KSA Non-Regulated Customers\)
+
+</td>
+<td valign="top">
+
+cf-sa31
+
+</td>
+<td valign="top">
+
+me-central2
+
+</td>
+<td valign="top">
+
+34.166.162.172, 34.166.125.210, 34.166.181.228, 34.166.70.80, 34.166.99.127, 34.166.92.192
+
+</td>
+<td valign="top">
+
+api.cf.sa31.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+sa31.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[https://emea.cockpit.btp.cloud.sap/](https://emea.cockpit.btp.cloud.sap/)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Google Cloud
+
+</td>
+<td valign="top">
+
 us30
 
 </td>

docs/10-concepts/regions-for-the-kyma-environment-557ec3a.md

@@ -7,7 +7,7 @@ To work with the Kyma environment, you need to specify the region for both your
 
 
 > ### Note:  
-> In the Kyma environment, IP addresses for NAT Gateway that handles the egress traffic are configured dynamically. This means that you cannot identify the IP address of NAT Gateway in advance. However, once the IP address is assigned, it remains unchanged throughout the cluster's lifecycle.
+> You can see the IP addresses for NAT Gateway that handles the egress traffic as values of the `cloud.natGatewayIps` parameter in the `kyma-info` ConfigMap in your Kyma instance. To check the NAT IPs, run `kubectl --namespace kyma-system get configmap kyma-info -o json | jq -r '.data["cloud.natGatewayIps"]'`.
 
 
 

docs/10-concepts/sap-btp-specific-configurations-9809fa4.md

@@ -56,4 +56,6 @@ The following technical configurations are specific to SAP BTP and differ from t
 
 -   Cloud Foundry Audit Events have a retention period of 14 days. For more information on Audit Events, see [https://docs.cloudfoundry.org/running/managing-cf/audit-events.html](https://docs.cloudfoundry.org/running/managing-cf/audit-events.html).
 
+-   To ensure the stable and fair operation of our platform, we enforce rate limiting on container network bandwidth. Specific thresholds are not disclosed to prevent abuse. These limits are carefully set to fully support all expected customer workload.
+
 

docs/10-concepts/service-plans-and-metering-for-cloud-foundry-runtime-8d41fa4.md

@@ -222,6 +222,38 @@ For information on how to set up the plan, see [Free Plan for Cloud Foundry Runt
 
 
 
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+\-
+
+</td>
+<td valign="top">
+
+Cloud Foundry Environment \(`cloudfoundry`\)
+
+</td>
+<td valign="top">
+
+build-runtime
+
+</td>
+<td valign="top">
+
+build-runtime
+
+</td>
+<td valign="top">
+
+This plan is only for using the SAP BTP, Cloud Foundry runtime as part of SAP Build. For more information, see [What Is SAP Build](https://help.sap.com/docs/build-service/build-service-guide/what-is-sap-build) and [Service Plans and Metering](https://help.sap.com/docs/build-service/build-service-guide/service-plans-and-metering).
+
+> ### Note:  
+> The plan is not depicted on the diagram in the **Overview** section.
+
+
+
 </td>
 </tr>
 <tr>