Control LoadBalancer service

[jvalkeal]

We don't distinguish LoadBalancer from NodePort, thus service name is derived from appId.

spring-cloud-deployer-kubernetes/src/main/java/org/springframework/cloud/deployer/spi/kubernetes/KubernetesAppDeployer.java

Lines 429 to 431 in 078cedc

	client.services().inNamespace(client.getNamespace()).createNew().withNewMetadata().withName(appId)
	.withLabels(idMap).withAnnotations(annotations).addToLabels(SPRING_MARKER_KEY, SPRING_MARKER_VALUE)
	.endMetadata().withSpec(spec.build()).done();

With skipper what we want to do is to have control over a created and used LoadBalancer because when we upgrade to a new app from v1 to v2, we may want to keep old LoadBalancer server and then labels of existing applications to potentially do canary deployments.

Maybe as simple as if same name for service exists, we don't need to create it and some sort of property to tell that with undeploy we want to keep service around.

[xetra11]

Really a needed feature!