Tenant Users Cannot Deploy Container Applications to a Cluster of Container Service Extension Instances Using a Routed Network

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:
If a tenant user attempts to deploy a container application to a cluster of Container Service Extension instances that is configured with a routed network, the operation fails.

Cause

When App Launchpad and Container Service Extension are deployed in a VMware Cloud environment, App Launchpad cannot reach the IP address of the cluster of Container Service Extension instances.

Resolution

This issue is resolved in App Launchpad 2.0.0.1.

Workaround:
If the tenant users encounter this problem, remap the IP address of the cluster.

1. Open an SSH connection to the App Launchpad machine.
2. Get a list of all Container Service Extension guest Kubernetes clusters by running the alp k8s-cluster list command.
   The system returns the following response:

   | Ref ID | Cluster Name | Org Name | External Address
   ------------------------------------------------------------ 
   <Cluster Ref ID> | IP-address-name-k8s-cluster | Org1 | <IP> 
   

   Copy the reference ID of the cluster that does not have an external address.

3. Set an external IP address mapping for the Kubernetes main node by running the following command.

   alp k8s-cluster set-address --cluster-ref-id=<Cluster Ref ID> --external-address=<NEW_IP>
   

   Upon a successful completion of the operation, the system returns the following response:

   Address is set successfully! +---------------------------------------+-----------
   
   | Ref ID | Cluster Name | Org Name | External Address
   ------------------------------------------------------------
   <Cluster Ref ID> | IP-address-name-k8s-cluster | Org1 | <NEW_IP> 
   

4. Restart App Launchpad services by running the systemctl restart alp command.