#routes:
# - {to: 192.168.12.0/22, via: 192.168.12.65}
+ ### Optional.
+ ### This network is used as the underlay network for inter-cluster
+ ### communication within CaaS. Setting this network can expose CaaS cluster
+ ### services to this network.
+ ### If unspecified, infra_internal used as a fallback option.
+ #caas_oam:
+ ### Optional network mtu
+ ### If not defined default value is used.
+ #mtu: <VALUE>
+
+ ### Network domains
+ #network_domains:
+ ### User defined name for network domain
+ #rack-1:
+ ### Network address in CIDR format
+ #cidr: <VALUE>
+
+ ### Optional vlan id
+ #vlan: <VALUE>
+
+ ### IP address of the gateway for default route.
+ ### If unspecified, the subnet's first IP address assumed.
+ #gateway: <VALUE>
+
+ ### Range for IPs
+ #ip_range_start: <VALUE>
+ #ip_range_end: <VALUE>
+
+ ### Optional static routes
+ #routes:
+ # - {to: <CIDR>, via: <IP>}
+
### Provider networks
### Provider network to physical interface mapping is done
### in the network profile configuration
### the Docker bridge CIDRs of all host via this parameter.
#docker0_cidr: "172.17.0.1/16"
+ ### This parameter is used to set the overlay CIDR of the default network for containers, so pods can comminucate
+ ### over this subnet and Kubernetes services are available here also.
+ ### The parameter can be used to make sure the CIDR of this network does not overlap with any customer
+ ### specific provider network's
+ #oam_cidr: "10.244.0.0/16"
+
### Mandatory parameter. All the infrastructure's HTTP servers are secured with TLS.
### The certificates of the servers are created in infrastructure deployment time, and are signed by an externally provided CA certificate.
### This CA certificate can be configured by setting its encrypted format into this configuration parameter.