spring-cloud
discoveryserver shouldn't use eureka's port
Describe the bug spring-cloud-netflix has been using port 8761 for default Eureka api endpoint since maybe the beginning a decade ago.
It is uncommon and surprising to use an established port from another project for a different API. For example, I wouldn't serve HTTP from port 53 just because it is similar data than you'd get from DNS.
Even if in k8s there's not likely a conflict, as we expect different hostnames to be used for eureka and discoveryserver in a migration use case, it is still IMHO a bug not a feature.
@jonatan-ivanov can be blamed for encouraging me to raise issues on things I think are bugs, so.. here we are!
I believe the discoveryserver port should be changed to not the same as eureka's, but anyway glad to be heard regardless of outcome.
Sample
specifically, the default properties and embedded yaml could be adjusted.
https://github.com/search?q=repo%3Aspring-cloud%2Fspring-cloud-kubernetes%208761&type=code
p.s. a tested gold copy of the deployment yaml is preferred to embedded doc
