Xiaoyun Ding

Suspect this is because the config content 'optional:configserver:' is treated as yaml as well and try to parse it.

I find that the `initial status` can be refreshed when `EurekaInstanceConfigBean` is reloaded. So one possible solution is to use Config Server to store `eureka.instance.initialStatus` and when want to swap...

@spencergibb Thanks for the response. May I double confirm that the operation `ServiceRegistry.setStatus()` happens in client app side? If that case, when should the client app set the value? Does...

@spencergibb I think the problem we found is caused by the obsolete client status. Even the server-side is aware of the blue/green swap, when the client lost connection due to...

Do we have a plan to improve this behavior that the client can be notified about the change? I believe this is a common issue for Eureka users.

@cppforlife Thanks for the suggestions. I have tried to use Kapp controller v0.38 and it can work with overlap package versions of different package repos. It is really cool. However,...

Thanks @kvmw for the clarification. It is clear now. @cppforlife I have one further question regarding to `PackageRepo`. Since registry resources are immutable, say `my-repo:1.0.0` always have `my-package:0.0.1` and `my-repo:1.0.0`...

Thanks for the quick response. I think I find the reason why the sidecar is removed. I am using https://openservicemesh.io/ and it will add an annotation to the namespace that...

Yes, I am able to make it works. Thanks a lot for the help.

Hi @joe-kimmel-vmw , from my understanding, if no defined liveness probe, k8s will try to restart the pod when the PID 1 process crash. However, I am not sure there...