vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Managing external provider credentials](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domains-manage-creds)



* [Viewing external provider credentials](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-manage-creds-view)
* [Removing external provider credentials](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-manage-creds-rm)



* [Managing domain secrets](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-manage-secrets)



* [Regenerating the certificate for an Ingress domain](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-manage-secrets-regen)
* [Delete an Ingress domain secret](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-manage-secrets-rm)





[Customizing ALB routing](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationscomm-ingress-annotations)



* [Adding a server port to a host header](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsadd-sport-hheader)
* [Routing incoming requests with a private ALB](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsalb_id_anno)
* [Authenticating apps with App ID](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsapp-id-authentication)
! ! !
<-- <section "id="section-validate-a-firewall-rule-expression-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.EXPRESSION: The filter expression. For example, ip.src eq 93.184.216.0. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-validate-a-firewall-rule-expression-options" "> --><-- <section "id="section-validate-a-firewall-rule-expression-examples" "> --> Examples Validate firewall-rule expression ip.src eq 93.184.216.0. ibmcloud cis firewall-rule-validate 31984fea73a15b45779fa0df4ef62f9b "ip.src eq 93.184.216.0" -i "cis-demo"
<-- </section "id="section-validate-a-firewall-rule-expression-examples" "> --><-- </section "id="section-validate-a-firewall-rule-expression" "> --><-- </section "id="section-firewall-rules" "> --><-- <section "id="section-glb" "> --> Global load balancer Manipulate global load balancers by using the following glb commands.<-- <section "id="section-create-glb" "> --> ibmcloud cis glb-create Create a global load balancer under a given DNS domain. ibmcloud cis glb-create DNS_DOMAIN_ID (--json @JSON_FILE | JSON_STRING) -i, --instance INSTANCE] --output FORMAT]
ibmcloud account domain-cert DOMAIN_NAME



 Command options 

DOMAIN_NAME (required)
: The domain that hosts the certificate.





 Examples 

View the certificate information of the domain ibmcxo-eventconnect.com:

ibmcloud account domain-cert ibmcxo-eventconnect.com







 ibmcloud account domain-cert-add 

Add a certificate to the specified domain in the current org:

ibmcloud account domain-cert-add DOMAIN -k PRIVATE_KEY_FILE -c CERT_FILE [-p PASSWORD] [-i INTERMEDIATE_CERT_FILE] [-t TRUST_STORE_FILE]



 Command options 

DOMAIN (required)
: The domain that the certificate is added to.

-k PRIVATE_KEY_FILE (required)
: The private key file path.

-c CERT_FILE (required)
: The certificate file path.

-p PASSWORD (optional)
: The password for the certificate.

-i INTERMEDIATE_CERT_FILE (optional)
: The intermediate certificate file path.

-t TRUST_STORE_FILE (optional)
: The truststore file.





 Examples 

Add a certificate to the domain ibmcxo-eventconnect.com:

ibmcloud account domain-cert-add ibmcxo-eventconnect.com -k key_file.key -c cert_file.crt -p 123 -i inter_cert.cert







 ibmcloud account domain-cert-remove 

Remove a certificate from the specified domain in current org:

ibmcloud account domain-cert-remove DOMAIN [-f]



 Command options 

DOMAIN (required)
: Domain to remove the certificate from.

-f (optional)
: Force deletion without confirmation.
To use a domain that you created yourself, such as a domain that is registered with an external provider, see [Setting up TLS secrets for custom subdomains](https://cloud.ibm.com/docs/containers?topic=containers-secretstls-custom).





 TLS secrets for IBM-managed Ingress domains 

Follow the steps to set up TLS secrets for the IBM-managed Ingress domain.



1. List the existing subdomains in your cluster. In the Subdomain column of the output, copy the subdomain that has the highest i00<n> value.

ibmcloud oc nlb-dns ls --cluster <cluster_name_or_id>

In this example output, the mycluster-a1b2cdef345678g9hi012j3kl4567890-i002.us-south.containers.appdomain.cloud subdomain has the highest i00<n> value of i002.

Subdomain Load Balancer Hostname Health Monitor SSL Cert Status SSL Cert Secret Name
mycluster-a1b2cdef345678g9hi012j3kl4567890-i000.us-south.containers.appdomain.cloud ["1234abcd-us-south.lb.appdomain.cloud"] None created mycluster-a1b2cdef345678g9hi012j3kl4567890-i000
mycluster-a1b2cdef345678g9hi012j3kl4567890-i001.us-south.containers.appdomain.cloud ["5678efgh-us-south.lb.appdomain.cloud"] None created mycluster-a1b2cdef345678g9hi012j3kl4567890-i001
* [Removing a domain from a cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-domainsingress-domains-manage-rm)
* [Updating a domain's IP addresses or hostname](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-domainsingress-domains-manage-update)
* [Changing a cluster's default domain](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-domainsingress-domain-manage-default)



* [Managing external provider credentials](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-domainsingress-domains-manage-creds)



* [Viewing external provider credentials](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-domainsingress-domain-manage-creds-view)
* [Removing external provider credentials](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-domainsingress-domain-manage-creds-rm)



* [Managing domain secrets](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-domainsingress-domain-manage-secrets)



* [Regenerating the certificate for an Ingress domain](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-domainsingress-domain-manage-secrets-regen)
* [Delete an Ingress domain secret](https://cloud.ibm.com/docs/openshift?topic=openshift-ingress-domainsingress-domain-manage-secrets-rm)





[Managing TLS and non-TLS certificates and secrets](https://cloud.ibm.com/docs/openshift?topic=openshift-secretssecrets)
control-plane-2 Host control-plane-2.ocp.dallas.ibm.local 192.168.133.12 
 compute-0 Host compute-0.ocp.dallas.ibm.local 192.168.133.13 
 compute-1 Host compute-1.ocp.dallas.ibm.local 192.168.133.14 
 compute-2 Host compute-2.ocp.dallas.ibm.local 192.168.133.15 
 Application wildcard DNS (Load Balancer) *.apps.ocp.dallas.ibm.local 10.208.242.131 
 Kubernetes API URL (Load Balancer) api.ocp.dallas.ibm.local 10.208.242.132 
 Kubernetes API-INT (Internal) URL (Load Balancer) api-int.ocp.dallas.ibm.local 10.208.242.132 
 etcd Node0 etcd-0.ocp.dallas.ibm.local 192.168.133.10 
 etcd Node1 etcd-1.ocp.dallas.ibm.local 192.168.133.11 
 etcd Node2 etcd-2.ocp.dallas.ibm.local 192.168.133.12 
 etcd Service Record Node 0 _etcd-server-ssl._tcp.ocp.dallas.ibm.local 192.168.133.10 
 etcd Service Record Node 1 _etcd-server-ssl._tcp.ocp.dallas.ibm.local 192.168.133.11 
 etcd Service Record Node 2 _etcd-server-ssl._tcp.ocp.dallas.ibm.local 192.168.133.12 









 DNS commands 

 Create Reverse Lookup Zones
Add-DnsServerPrimaryZone -networkid "192.168.133.0/24" -replicationscope forest
Add-DnsServerPrimaryZone -networkid "10.208.242.0/24" -replicationscope forest

 Create DNS A Records, with PTR
* [Updating a custom domain mapping with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsupdate-custom-domain-cli)



* [Deleting domain mappings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsdelete-custom-domain)



* [Deleting domain mappings from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsdelete-custom-domain-ui)
* [Deleting domain mappings with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-domain-mappingsdelete-custom-domain-cli)









 Running jobs 

[Working with jobs and job runs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-planjob-plan)



* [How do I make my code run as a Code Engine job component?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-planjob-containerimage)
* [Considerations for HTTP handling](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-planconsiderationshttphandlingjob)
* [Options for creating and running a job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-planjob-options)



* [Memory and CPU for jobs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-planjob-options-combo)
* [Creating and running a job with commands and arguments](https://cloud.ibm.com/docs/codeengine?topic=codeengine-job-planjob-cmd-args)
Run this command to store it in variable DNS_ZONE_ID:

DNS_ZONE_ID="example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae"





 Getting a DNS zone 

Use the ibmcloud dns zone command followed by the zone ID to get details of an existing zone.

$ ibmcloud dns zone $DNS_ZONE_ID
Getting zone 'example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae' for service instance 'DNS Services-km' ...
OK

ID example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae
Name example.com
Description
Label
State PENDING_NETWORK_ADD
Created On 2020-04-10 07:21:51.774444868 +0000 UTC
Modified On 2020-04-10 07:21:51.774444868 +0000 UTC





 Updating a DNS zone 

Use the ibmcloud dns zone-update command followed by the zone ID to update a zone. Specify -d, --description to update the description and/or -l, --label to update the label of a zone.

$ ibmcloud dns zone-update $DNS_ZONE_ID -d "example zone" -l "us-south"
Updating zone 'example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae' for service instance 'DNS Services-km' ...
OK

ID example.com:f7f40364-a5e6-48f7-9fc9-387434c579ae
Name example.com
Description example zone
Label us-south
State PENDING_NETWORK_ADD
Created On 2020-04-10 07:21:51.774444868 +0000 UTC
!! ] ! ! ! ! !
<-- <section "id="section-command-options-logpush-job-create" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.--destination value: Specify a COS bucket path or a LogDNA path where data will be pushed.
<-- <ul> -->

* Syntax for LogDNA Path: https://{LOGS_REGION_URL}?hostname={DOMAIN}&apikey={LOGDNA_INGRESS_KEY}

Example: 'https://logs.eu-de.logging.cloud.ibm.com/logs/ingest?hostname=testv2_logpush&apikey=xxxxxx' Syntax for COS Path: cos://<BUCKET_OBJECT_PATH>?region=<REGION>&instance-id=<IBM_ClOUD_OBJECT_STORAGE_INSTANCE_ID> Example: 'cos://cis-test-bucket/logs?region=us&instance-id=f75e6d90-4212-4026-851c-d572071146cd' To separate logs into daily subfolders, use the special string {DATE} in the bucket path. It will be substituted with the date in YYYYMMDD format, for example '20190423'. Subfolders will be created as appropriate, for example: 'cos://cis-test-bucket/logs/{DATE}?region=us&instance-id=f75e6d90-4212-4026-851c-d572071146cd'

<-- </ul> -->

--name value: Job name. Required.--enable value: Enable the job or not. The job is disabled by default.--fields value: Define the list of log fields to be included in log files. Multiple fields can be separated by commas and use command [ibmcloud cis logpush-available-fields DNS_DOMAIN_ID to get the comprehensive list of available log fields, or use all to include all available fields in log files.
Show more

The information in the following table represents the configuration above:



Table 1: Configuration information

 Interface name Interface function Redundant interface 

 ge-0/0/1 / ge-0/0/2 Gigabit ethernet interface for SL-PRIVATE transit VLAN on node 0 reth0 
 ge-0/0/3 / ge-0/0/4 Gigabit ethernet interface for SL-PUBLIC transit VLAN on node 0 reth1 
 ge-0/0/5 / ge-0/0/6 Gigabit ethernet interface for Customer Private VLAN on node 0 reth2 
 ge-0/0/7 / ge-0/0/8 Gigabit ethernet interface for Customer Public VLAN on node 0 reth3 
 ge-7/0/1 / ge-7/0/2 Gigabit ethernet interface for SL-PRIVATE transit VLAN on node 1 reth0 
 ge-7/0/3 / ge-7/0/4 Gigabit ethernet interface for SL-PUBLIC transit VLAN on node 1 reth1 
 ge-7/0/5 / ge-7/0/6 Gigabit ethernet interface for Customer Private VLANs on node 1 reth2 
 ge-7/0/7 / ge-7/0/8 Gigabit ethernet interface for Customer Public VLANs on node 1 reth3 
 fab0 Chassis cluster fabric link uses ge-0/0/0 and ge-0/0/9 
 fab1 Chassis cluster fabric link uses ge-7/0/0 and ge-7/0/9 
 fxp0 Management interface 
 lo0 loopback interface 







 Interface configurations 

The legacy architecture for these configurations leveraged Linux bridging on the Ubuntu host hypervisor. IBM has since transitioned to a new architecture for its gateways that leverages SR-IOV on the host. This caused the vSRX configuration’s interface mapping to change in many cases. Differences in the interface configuration are also influenced by whether the vSRX is:



* 10G or 1G
* Standalone or High Availability
* Public and Private, or Private Only
* The vSRX Version



* All 15.1 based vSRX’s use the legacy architecture
Use the IBM Cloud global catalog to list zones within the desired region. This field is required for, and only applicable to, network type gre_tunnel and unbound_gre_tunnel connections. 
 <br><br> * name <br> string<br><br><br> Availability zone name. <br>Example:us-south-1 





 Example Request 

This example illustrates adding a connection to the transit gateway with the API:

curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "network_type": "vpc" }'
"
{base_url}/transit_gateways/{transit_gateway_id}/connections?version={version}"

"base_connection_id": "975f58c1-afe7-469a-9727-7f3d720f2d32",
"local_gateway_ip": "192.168.100.1",
"local_tunnel_ip": "192.168.129.2",
"name": "Transit_Service_BWTN_SJ_DL",
"network_account_id": "28e4d90ac7504be694471ee66e70d0d5",
"network_id": "crn:v1:bluemix:public:is:us-south:a/123456::vpc:4727d842-f94f-4a2d-824a-9bc9b02c523b",
"network_type": "vpc",
"prefix_filters": [
{
"action": "permit",
"ge": 0,
"le": 32,
"prefix": "192.168.100.0/24"
}
],
"prefix_filters_default": "permit",
"remote_bgp_asn": 65010,
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e8ff9d475c01bcec23b567bb9ca41b247bc46dbb/citrix-netscaler-vpx/icons/checkmark-icon.svg) 
 Layer 4 load balancer ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e8ff9d475c01bcec23b567bb9ca41b247bc46dbb/citrix-netscaler-vpx/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e8ff9d475c01bcec23b567bb9ca41b247bc46dbb/citrix-netscaler-vpx/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e8ff9d475c01bcec23b567bb9ca41b247bc46dbb/citrix-netscaler-vpx/icons/checkmark-icon.svg) 
 Layer 7 load balancer ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e8ff9d475c01bcec23b567bb9ca41b247bc46dbb/citrix-netscaler-vpx/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e8ff9d475c01bcec23b567bb9ca41b247bc46dbb/citrix-netscaler-vpx/icons/checkmark-icon.svg) !
13.101.0.0/24 from VPC B through Transit Gateway (local) 
 10.0.0.0/8 from an Enterprise through Direct Link 
 172.16.0.0/12 from an Enterprise through Direct Link 
 13.0.0.0/8 from an Enterprise through Direct Link 



VPC A Default (Egress) Routing Table

VPC B Default (Egress) Routing Table



Table 6. VPC A Default (Egress) Routing Table

 Destination Action Next Hop Location 

 13.0.0.0/8 Delegate-VPC <br><br> * <br><br><br> Dallas 1 
 13.0.0.0/8 Delegate-VPC <br><br> * <br><br><br> Dallas 2 
 13.0.0.0/8 Delegate-VPC <br><br> * <br><br><br> Dallas 3 







 Use case 2: VPC-to-VPC connected with IBM Cloud Transit Gateway 

Zoom

![VPC-to-VPC connected with Transit Gateway use case](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/vpc-vpc-transit-gateway.png)

VPC-to-VPC connected with Transit Gateway

VPC A Networks

VPC B Networks

VPC Z Networks



Table 8. VPC A Networks

 IP Origin 

 10.100.0.0/24 from VPC A subnet 
 13.100.0.0/24 from VPC A subnet 
 10.101.0.0/24 from VPC B through Transit Gateway (local) 
 13.101.0.0/24 from VPC B through Transit Gateway (local) 
 10.111.0.0/24 from VPC Z through Transit Gateway (global) 
 13.111.0.0/24 from VPC Z through Transit Gateway (global) 



VPC A Default (Egress) Routing Table
"href": "https://eu-gb.iaas.cloud.ibm.com/v1/load_balancers/r018-808fedde-2650-46cc-9cd1-4b828b92970a/listeners/r018-3811d7ad-3bbe-4cb4-82de-8608f767866a",
"id": "r018-3811d7ad-3bbe-4cb4-82de-8608f767866a",
"port": 200,
"protocol": "tcp",
"provisioning_status": "update_pending"
}
[High availability for VPC reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-high-availabilityvpc-architecture-high-availability)



* [Your workloads on VPC infrastructure](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-high-availabilityyour-workloads)



* [Workloads in multizone regions](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-high-availabilityyour-workloads-multizone)
* [Workloads in multiple regions](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-high-availabilityyour-workloads-multiple-regions)



* [HA for IBM Cloud services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-high-availabilityibm-cloud-services)
* [Related controls in IBM Cloud Framework for Financial Services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-high-availabilityrelated-controls)
* [Next steps](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-high-availabilitynext-steps)



[High availability for Satellite reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-high-availabilitysatellite-architecture-high-availability)



* [High availability in your Satellite location](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-high-availabilityyour-workloads)
* ibmcloud is load-balancer-listener-policy-create 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --name my-policy --action reject --priority 5 The priority of the policy can have a range of 1 to 10, where a lower value indicates a higher priority. The possible values for action are "forward", "redirect", or "reject".
* ibmcloud is load-balancer-listener-policy-create my-lb 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --name my-policy --action reject --priority 5 The priority of the policy can have a range of 1 to 10, where a lower value indicates a higher priority. The possible values for action are "forward", "redirect", or "reject".
* ibmcloud is load-balancer-listener-policy-create 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --action forward --priority 2 --target 70294e14-4e61-11e8-bcf4-0242ac110004 When the action is forward, the pool ID or name is required to specify which pool the load balancer forwards the traffic to.
* ibmcloud is load-balancer-listener-policy-create my-lb 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --action forward --priority 2 --target my-pool When the action is forward, the pool ID or name is required to specify which pool the load balancer forwards the traffic to.
* [Parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driveraws-ebs-csi-driver-parameter-reference)



* [1.1.0 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driveraws-ebs-csi-driver-1.1.0-parameters)
* [1.5.1 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driveraws-ebs-csi-driver-1.5.1-parameters)
* [1.12.0 parameter reference](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driveraws-ebs-csi-driver-1.12.0-parameters)



* [Storage class reference for AWS EBS](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driversat-ebs-sc-reference)
* [Getting help and support for AWS EBS](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-ebs-csi-driversat-ebs-support)



[AWS EFS](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-efs-csi-driverstorage-aws-efs-csi-driver)



* [Prerequisites for using AWS EFS](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-aws-efs-csi-driversat-storage-efs-prereqs)
<br>This field is used when gateway connection is in network type classic. <br>This field is required to be unspecified for network type gre_tunnel. <br>Example:28e4d90ac7504be694471ee66e70d0d5 
 network_id <br>string The ID of the network being connected via this connection. This field is required for vpc and directlink. This is the target CRN for network type vpc or directlink. <br>This field is required to be unspecified for network type classic, gre_tunnel, and unbound_gre_tunnel connections. <br>Example:crn:v1:bluemix:public:is:us-south:a/123456::vpc:4727d842-f94f-4a2d-824a-9bc9b02c523b 





 Example request 

This example illustrates the original account requesting a cross-account connection:

curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "network_type": "vpc" }'
"
{base_url}/transit_gateways/{transit_gateway_id}/connections?version={version}"

"name": "Transit_Service_BWTN_SJ_DL",
"network_id": "crn:v1:bluemix:public:is:us-south:a/123456::vpc:4727d842-f94f-4a2d-824a-9bc9b02c523b",
"network_type": "vpc",
"prefix_filters": [
{
"action": "permit",
"ge": 0,
"le": 32,
"prefix": "192.168.100.0/24"
}
],
"prefix_filters_default": "permit",







 Response
[Classic: About network load balancers (NLBs)](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-aboutloadbalancer-about)



* [Comparison of basic and DSR load balancing in version 1.0 and 2.0 NLBs](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-aboutcomparison-lbs)
* [Components and architecture of an NLB 1.0](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-aboutv1_planning)



* [Traffic flow in a single-zone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-aboutv1_single)
* [Traffic flow in a multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-aboutv1_multi)



* [Components and architecture of an NLB 2.0](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-aboutplanning_ipvs)



* [Traffic flow in a single-zone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-aboutipvs_single)
* [Traffic flow in a multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancer-aboutipvs_multi)





[Classic: Setting up basic load balancing with an NLB 1.0](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancerloadbalancer)



* [Setting up an NLB 1.0 in a multizone cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-loadbalancermulti_zone_config)