github.com/kyma-project/kyma-environment-broker@v0.0.1/docs/user/04-30-custom-networking-configuration.md (about)

     1  # Custom networking configuration
     2  
     3  To create a Kyma runtime with a custom IP range for worker nodes, specify the additional `networking` provisioning parameters. See the example:
     4  
     5  ```bash
     6     export VERSION=1.15.0
     7     curl --request PUT "https://$BROKER_URL/oauth/v2/service_instances/$INSTANCE_ID?accepts_incomplete=true" \
     8     --header 'X-Broker-API-Version: 2.14' \
     9     --header 'Content-Type: application/json' \
    10     --header "$AUTHORIZATION_HEADER" \
    11     --header 'Content-Type: application/json' \
    12     --data-raw "{
    13         \"service_id\": \"47c9dcbf-ff30-448e-ab36-d3bad66ba281\",
    14         \"plan_id\": \"4deee563-e5ec-4731-b9b1-53b42d855f0c\",
    15         \"context\": {
    16             \"globalaccount_id\": \"$GLOBAL_ACCOUNT_ID\"
    17         },
    18         \"parameters\": {
    19             \"name\": \"$NAME\",
    20             \"region\": \"$REGION\",
    21             \"networking\": {
    22                \"nodes\": \"10.250.0.0/20\"
    23             }
    24         }
    25     }"
    26  ```
    27  > **NOTE:** The `nodes` value is a mandatory field, but the `networking` section is optional.
    28  
    29  If you do not provide the `networking` object in the provisioning request, the default configuration is used.
    30  The configuration is immutable - it cannot be changed later in an update request.
    31  The provided IP range must not overlap with ranges of potential seed clusters (see [GardenerSeedCIDRs definition](https://github.com/kyma-project/kyma-environment-broker/blob/main/internal/networking/cidr.go)).
    32  The suffix must not be greater than 23 because the IP range is divided between the zones and nodes. Additionally, two ranges are reserved for `pods` and `services` which also must not overlap with the IP range for nodes.
    33