discoveryserver shouldn't use eureka's port about spring-cloud-kubernetes HOT 6 CLOSED

I am a big fan of @jonatan-ivanov and I agree with him, I think the community should open issues if they have concerns about anything.

However in this case I still do not see how using the same port as Eureka is a "bug". I could easily choose another port but there could be some other application else where that uses that port...so we could be in the same situation.

Unless you can show an example of how using the same port is causing an issue or is keeping you from implementing a use case/solution I don't think there is a need to change it.

from spring-cloud-kubernetes.

I can understand that since you chose to do this, you would prefer it the same way. I wonder if anyone else in reflection thinks similar to me, that it is a needless opportunity for conflict. If someone wants to migrate from eureka to this, there will be an unnecessary conflict while that migration is occurring. That said, I won't try to help anyone do that, so indeed I'll leave it to an end user and/or stack overflow.

Y'all can choose to close this, as I feel heard even if don't agree still, as no new information was provided that would make this a better choice than it was when I opened it.

from spring-cloud-kubernetes.

I don't see where the "conflict" will occur.

from spring-cloud-kubernetes.

conflict is there if there's one pod for discovery, right?

a pod includes eureka and discoveryserver, you want to transition some applications to the discoveryserver while others haven't moved yet.

This is generally why people don't choose the same port as well established servers, for unrelated servers. Like I wouldn't choose consul's port for eureka, etc. there's no chance of conflict so you don't need to think through things like this. Choosing the same port makes this stuff possible.

from spring-cloud-kubernetes.

But this only would happen if you are running eureka and the discovery server in the same container, which begs the use case as to why you would do that?

from spring-cloud-kubernetes.

I think we are going around in circles

• why would you choose the same port as an established thing
• why would you deploy something in the way it can conflict with an established thing

I see in spring docs, notes some times about "avoid doing X" that's a solution. Another is to eliminate the problem. I'm for the latter as it is simpler (to not have the problem). If keeping this issue open means endless circles on the same points with no new information, I'll just close it. Someone else can open it, but I don't want to spend more time explaining this. No offense, just this is a time budget thing and I think there's diminishing returns at this point.

from spring-cloud-kubernetes.