Deploy Enterprise PKS by Importing a YAML Configuration File

Page last updated:

If you have an existing YAML configuration file from a previous deployment of VMware Enterprise PKS, you can use the VMware Enterprise PKS Management Console to deploy a new Enterprise PKS instance from that file.

Notes: You can only use the management console to deploy Enterprise PKS from a YAML file if that YAML file was generated by Enterprise PKS Management Console version 1.0 or later. YAML files from beta releases of the management console are not compatible with this release.

You can import a YAML from an earlier supported version of Enterprise PKS Management Console. In this case, after you import the YAML, open the configuration in the wizard and configure any missing settings that are new in this version.

For information about how to deploy Enterprise PKS by using the configuration wizard, see Deploy Enterprise PKS by Using the Configuration Wizard.

For information about how to upgrade an existing deployment, see Upgrade Enterprise PKS Management Console.

YAML Files and Passwords

When Enterprise PKS Management Console generates the content of the YAML file for the YAML editor, it masks the passwords for NSX Manager, vCenter Server, and Harbor so that they do not appear in plain text. In the generated YAML files, the password fields look like the following example:

admin_password: <hidden:f065be51-84e9-4ca7-972d-ed46f7273123>

The <hidden> tag includes a GUID that refers to a database entry for the password that was entered into the configuration wizard. If you import a YAML file from an instance of Enterprise PKS Management Console that is deployed in a different vSphere environment, the GUID provided in the hidden tag will not correspond to an entry in the database of the environment in which you are importing the YAML. As a consequence, if you import a YAML from a different vSphere environment, you must manually update the passwords for NSX Manager, vCenter Server, and Harbor in the YAML editor. If you are importing a YAML file from the same environment, the correct passwords are held in the database and no action is required.

Prerequisites

Import a YAML Configuration File

  1. On the VMware Enterprise PKS landing page, click Install then Import Configuration File. Start configuration wizard or import YAML file View a larger version of this image
  2. Drag the YAML file into the Import Configuration File window, or click Browse to navigate to it.
  3. In the Configuration File editor, modify the contents of the YAML file appropriately for the new instance of Enterprise PKS that you want to deploy.

    Apply the generated YAML configuration View a larger version of this image

    If the YAML was generated by an instance of management console that is running in a different vSphere environment, update the passwords for NSX Manager, vCenter Server, and Harbor.

    You can click the Edit in Wizard button, to open the imported configuration in the wizard and modify it there. For example, if you have imported a YAML that was generated by a previous version of Enterprise PKS Management Console, open it in the wizard so that you can configure any options that are new in this version.

    To abandon this YAML and start again, click Import YAML to upload the YAML again or to import a new one.

  4. When you have finished editing the YAML in the Configuration File editor, click Export YAML to save a copy of your updated YAML configuration.

  5. Click Apply Configuration and Continue to deploy Enterprise PKS from this configuration file.

  6. On the PKS Configuration page, follow the progress of the deployment.

  7. When the deployment has completed successfully, click Continue to monitor and manage your deployment.

A successful Enterprise PKS deployment View a larger version of this image

Networking Options in the YAML File

The networking parameters for the three types of Enterprise PKS networking are all included in the network: section of the YAML file. When you edit the YAML file, you only need to set those parameters that apply to your type of networking.

The following table lists the parameters to set for each type of networking.

Unprepared NSX-T Data Center Prepared NSX-T Data Center Flannel

active_t0_edge_node
active_t0_edge_node_ip
additional_dep_reserved_ip_range
autoprovision_nsx
dep_dns
dep_network_cidr
dep_reserved_ip_range_from
dep_reserved_ip_range_to
external_portgroup_gateway
external_portgroup_netmask
external_portgroup_subnet
external_vlan_id
floating_ips_range
nsx_manual_ssl_certs
nsx_ca_crt
nsx_dns
nsx_host
nsx_node_cidr
nsx_password
nsx_pod_cidr
nsx_username
nsx_verify_ssl_certs
ntp_servers
opsman_fqdn
standby_t0_edge_node
standby_t0_edge_node_ip
t0_edge_node_lb_ip
t0_ha_mode_active_active
use_nsx

additional_dep_reserved_ip_range
autoprovision_nsx
dep_dns
dep_network_name
dep_reserved_ip_range_from
dep_reserved_ip_range_to
ntp_servers
nsx_ca_crt
nsx_dns
nsx_fip_id
nsx_host
nsx_manual_ssl_certs
nsx_nat_mode
nsx_node_ip_block_id
nsx_password
nsx_pod_ip_block_id
nsx_t0_id
nsx_username
nsx_verify_ssl_certs
opsman_fqdn
use_nsx
additional_dep_reserved_ip_range
additional_svc_reserved_ip_range
dep_dns
dep_network_cidr
dep_network_gateway
dep_network_name
dep_reserved_ip_range_from
dep_reserved_ip_range_to
flannel_pod_network_cidr
flannel_service_network_cidr
ntp_servers
opsman_fqdn
svc_dns
svc_network_name
svc_network_cidr
svc_network_gateway
svc_reserved_ip_range_from
svc_reserved_ip_range_to
use_nsx

Next Steps

You can now access the Enterprise PKS control plane and begin deploying Kubernetes clusters. For information about how to deploy clusters directly from the management console, see Create and Manage Clusters in the Management Console.

For information about how you can use Enterprise PKS Management Console to monitor and manage your Enterprise PKS deployment, see Monitor and Manage Enterprise PKS in the Management Console.

Important: If you deployed Enterprise PKS with plans that use Windows worker nodes, see Enable Plans with Windows Worker Nodes for information about how to install a Windows Server stemcell and other necessary configuration actions that you must perform. Plans that use Linux worker nodes are available immediately, but plans that use Windows worker nodes are ignored until you install the Windows Server stemcell.

If Enterprise PKS fails to deploy, see Troubleshooting.


Please send any feedback you have to pks-feedback@pivotal.io.