Troubleshooting Enterprise PKS Management Console

Page last updated:

Warning: VMware Enterprise PKS v1.6 is no longer supported because it has reached the End of General Support (EOGS) phase as defined by the Support Lifecycle Policy. To stay up to date with the latest software and security updates, upgrade to a supported version.

The following sections describe how to troubleshoot failures to deploy of the VMware Enterprise PKS Management Console appliance and of Enterprise PKS instances from the management console.

Deployment of the Enterprise PKS Management Console Appliance Fails

Problem

Enterprise PKS Management Console appliance fails to deploy from the OVA template.

Solution

  1. Use SSH to log in to the Enterprise PKS Management Console appliance VM as root user.
    Use the password that you specified when you deployed the OVA.
  2. Run the following command to obtain the server logs:

    journalctl -u pks-mgmt-server > server.log
    
  3. If the logs do not provide the solution, delete the appliance VM from vCenter Server and attempt to deploy it again.

Deployment of Enterprise PKS from the Management Console Fails

Problem

Enterprise PKS fails to deploy from the management console.

Solution

  1. Follow the procedure in Delete Your Enterprise PKS Deployment to cleanly remove all Enterprise PKS components from vSphere and to clean up related objects in the management console appliance.
  2. Attempt to deploy Enterprise PKS again.

Enterprise PKS Management Console Cannot Retrieve Cluster Data in a Multi-Tier0 Topology

Problem

In a deployment to a multiple-tier0 topology, Enterprise PKS Management Console cannot display cluster information when you go to Enterprise PKS > Clusters and select a cluster. You see errors of the following type:

Failed to retrieve current K8s Cluster summary. cannot get cluster details: cannot get cluster namespaces: Get https://<address>:8443/api/v1/namespaces: dial tcp <address>:8443: i/o timeout
Failed to retrieve current K8s Cluster Volumes. cannot get namespaces of cluster 0116663b-f27b-4026-87e3-cddd01af41f2: Get https://<address>:8443/api/v1/namespaces: dial tcp <address>:8443: i/o timeout

Cause

In a single tier0 topology, Enterprise PKS Management Console is deployed to the same infrastructure network as vSphere and NSX-T Data Center. In a multiple-tier0 topology, due to tenant isolation, the infrastructure network is not routable to tenant tier0 uplink networks. In a multiple-tier0 topology, data from the Kubernetes API is exposed by floating IP addresses on tenant tier0 routers. Consequently, the management console cannot retrieve cluster data from the Kubernetes API because it is not on the same network as the tenants.

Solution

Make sure that the Enterprise PKS Management Console can connect to tenant floating IP addresses.

  1. Connect to the management console VM by using ssh.
  2. Configure a route on the management console appliance VM. For example, run the following command:
    route add -net <destination_subnet> gw <gateway_address>
    • Destination subnet: The network CIDR of the tenant floating IP addresses.
    • Gateway: A VM that can reach the tenant floating IP addresses and the management console.

Because the gateway can reach both the management console and the tenant floating IP addresses, the management console can reach the tenants and retrieve cluster data from the Kubernetes API.

Obtain the vRealize Log Insight Agent ID for Enterprise PKS Management Console

If you enabled integration with VMware vRealize Log Insight, Enterprise PKS Management Console generates a unique vRealize Log Insight agent ID for the appliance. You must provide this agent ID to vRealize Log Insight so that it can pull the appropriate logs from the appliance.

You obtain the vRealize Log Insight agent ID as follows:

  1. Use SSH to log in to the Enterprise PKS Management Console appliance VM as root user.
  2. Run the following command to obtain the ID:

    grep LOGINSIGHT_ID /etc/vmware/environment | cut -d= -f2
    

    The resulting ID will be similar to 59debec7-daba-4770-9d21-226ffd743843.

  3. Log in to the vRealize Log Insight Web user interface as administrator and add the agent ID to your list of agents.


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