Orphaned load balancer after deleting application with an Ingress

[pgoldtho]

Marketplace apps that include an Ingress may leave orphaned network components after deletion. The issue occurs in instances with long names.

The GKE Ingress Controller creates a load balancer to support the Ingress. A name is generated for the load balancer using the namespace, instance name and app name concatenated with a prefix and suffix. The maximum length for this name appears to be 64 characters. The issue occurs if the name gets truncated.

To reproduce, select the Wordpress application from Marketplace and create an instance passing test-nat-ns as the namespace and wordpress-1-superlongname-999999 as the instance name. Check the Enable public IP address checkbox and press Deploy.

Wait for the application to deploy, test it (it appears to work fine) then delete. Navigate to Network services -> Load balancing. You should see an orphaned resource called
k8s-um-test-nat-ns-wordpress-1-superlongname-999999-wordpress-0. It needs to be deleted manually. Now go to VPC network -> External IP addresses. It has a static IP address called k8s-fw-test-nat-ns-wordpress-1-superlongname-999999-wordpress-0. It also needs to be deleted manually.

[pgoldtho]

The issue occurs when the combined length of the x-google-marketplace: NAME and NAMESPACE properties exceeds 37 characters.