[GitHub] [servicecomb-java-chassis] huanghezhen opened a new issue #2559: 对于灰度发布的一个猜想

[GitBox <gi...@apache.org>]

huanghezhen opened a new issue #2559:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2559


   我看如果使用service center来实现灰度发布的时候,需要做配置,每次升级需要指定新实例的版本 比较麻烦
   所以我想可以不可以结合k8s的自己的健康机制来实现,
   比如 我将每个服务发布到注册中心的地址都是deployment的ip地址(这个我还没验证过,不同的服务是否可以注册相同的地址)
   然后 k8s 自己本身配置了健康检测,这样service center就不需要及时的知道哪个下线 从而避免空档期的error


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [servicecomb-java-chassis] liubao68 commented on issue #2559: 对于灰度发布的一个猜想

[GitBox <gi...@apache.org>]

liubao68 commented on issue #2559:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2559#issuecomment-915809984


   你的思路解决的是滚动升级不断服的问题，重要的是合理管理优雅下线等。 灰度发布是更加复杂的路由管理。


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [servicecomb-java-chassis] huanghezhen closed issue #2559: 对于灰度发布的一个猜想

[GitBox <gi...@apache.org>]

huanghezhen closed issue #2559:
URL: https://github.com/apache/servicecomb-java-chassis/issues/2559


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org