How to handle 'zombie' services when deployment fails

[popadynetsb]

Skipper creates a Service Object before the Deployment . As Skipper does not validate k8s Objects before trying to deploy an application and does not remove the service if the deployment fails, typos in a volume or volume mounts definitions result in zombie services. Now, on the next try, Skipper fails on deploying the service (as it is already present) and fixed component cannot be deployed

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

Lines 115 to 122 in 2772716

	createService(request);
	if (indexed) {
	createStatefulSet(request);
	}
	else {
	createDeployment(request);
	}
	return appId;