When you set up the VMware Cloud Director Container Service Extension configuration file, you can include the following 3 optional sections:

  • vcs

  • template_rules

  • extra_options

vCenter

This properties in this section detail the credentials that are necessary for the following operations:

  • Guest Operation Program Execution

  • Guest Operation Modifications

  • Guest Operation Queries

Each vCenter under the vcs section has the following properties:

Note:

If no_vc_communication_mode is set to False, all vCenter servers registered with VMware Cloud Director must be listed here, otherwise VMware Cloud Director Container Service Extension server installation or startup fails during pre-check phase. However, if no_vc_communication_mode is set to True, you can omit the entire vcs section.

Template Rules

Note:

template_rules section is not applicable when VMware Cloud Director Container Service Extension 3.1 is configured in non_legacy mode

Note:

This section was added in VMware Cloud Director Container Service Extension 2.5.0 and deprecated in VMware Cloud Director Container Service Extension 3.0.0

You can create rules to override some of the default attributes of templates that the remote template repository defines.

This section can contain zero or more such rules and each rule matches exactly one template. Matching is generated by name and revision of the template. It is necessary to specify both the name and revision, otherwise the rule will not process. Each rule comprises of the following attributes:
Table 1. template_rules properties and values

Property

Value

name

Name of the rule

target

Name and revision of the template on which the rule will be applied

action

Template properties that will be overridden. Only supported properties are compute_policy, cpu, and memory
For further details on compute policies, refer to Restricting Kubernetes templates

Extra Options

VMware Cloud Director Container Service Extension 3.1.2 added the extra_options fields tkgm_http_proxy, tkgm_https_proxy, and tkgm_no_proxy. These fields allow providers to specify proxy details that are injected into TKG Clusters. The proxy allows TKG clusters to reach out to the internet to download packages, such as Cloud Provider for VMware Cloud Director. VMware Cloud Director Container Service Extension injects the value of these variables into http-proxy.conf file on each node of the cluster. Proxy injection is supported for TKG clusters only.

Table 2. extra_options properties and values

Property

Value

tkgm_http_proxy

URL of the http proxy server

tkgm_https_proxy

URL of the https proxy server

tkgm_no_proxy

Comma separated list of IP addresses. Network traffic to these destinations does not use the proxy.

VMware Cloud Director Container Service Extension 3.1.3 added the extra_options fields cpi_version, csi_version, and antrea_version: These fields are supported only for TKG clusters.

Table 3. cpi_version, csi_version, antrea_version properties and values

Property

Value

cpi_version

CPI version in quotes

csi_version

CSI version in quotes

antrea_version

antrea version in quotes
If the user does not specify CPI, CSI, or antrea version in the cluster spec (see more here), then the VMware Cloud Director Container Service Extension server uses the CPI, CSI, or antrea version used in this section. These parameters are all optional, and the following defaults are used if these versions are not specified:
Table 4. cpi_version, csi_version, antrea_version default versions

Property

Version

cpi_version

1.1.1

csi_version

1.2.0

antrea_version

VMware Cloud Director Container Service Extension finds a TKG compatible antrea version if no antrea version is specified in the VMware Cloud Director Container Service Extension server config or in the cluster spec

 
extra_options:
  tkgm_http_proxy: http://192.168.7.10:3128
  tkgm_https_proxy: https://192.168.7.10:3128
  tkgm_no_proxy: localhost,127.0.0.1,192.168.7.0/24
  cpi_version: "1.1.1"
  csi_version: "1.2.0"
  antrea_version: "0.11.3"