X-Git-Url: https://gerrit.akraino.org/r/gitweb?p=ta%2Fconfig-manager.git;a=blobdiff_plain;f=userconfigtemplate%2Fuser_config.yaml;h=fdf6bdee14ca0de23a31169d5d4f58dbdcccd8c6;hp=2664b1fac0e4e059683f21487f255e43d158538b;hb=refs%2Fheads%2Fmaster;hpb=82b7d75b8609bec0f3086d93b2162375ba71e961 diff --git a/userconfigtemplate/user_config.yaml b/userconfigtemplate/user_config.yaml index 2664b1f..fdf6bde 100644 --- a/userconfigtemplate/user_config.yaml +++ b/userconfigtemplate/user_config.yaml @@ -172,6 +172,38 @@ networking: #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: + + ### Network domains + #network_domains: + ### User defined name for network domain + #rack-1: + ### Network address in CIDR format + #cidr: + + ### Optional vlan id + #vlan: + + ### IP address of the gateway for default route. + ### If unspecified, the subnet's first IP address assumed. + #gateway: + + ### Range for IPs + #ip_range_start: + #ip_range_end: + + ### Optional static routes + #routes: + # - {to: , via: } + ### Provider networks ### Provider network to physical interface mapping is done ### in the network profile configuration @@ -235,6 +267,12 @@ caas: ### 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.