[GitHub] [dubbo-go] AlexStocks opened issue #458: Imp: change k8s labels

["AlexStocks (GitHub)" <gi...@apache.org>]

<!-- Please only use this template for submitting enhancement requests -->

**What would you like to be added**:

![image](https://user-images.githubusercontent.com/7959374/77813142-26da1380-70e1-11ea-8d9e-c4d17e1f1bf0.png)

If the provider wanna register to k8s, its label should be `"dubbo.io/label":"dubbo.io.provider"` while the consumer label should be `"dubbo.io/label":"dubbo.io.consumer"`.

**Why is this needed**:

To get less data while consumer list&watch api server.

[ Full content available at: https://github.com/apache/dubbo-go/issues/458 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [dubbo-go] sxllwx commented on issue #458: Imp: change k8s labels

["sxllwx (GitHub)" <gi...@apache.org>]

Hello, although the separate registration of Provider and Consumer can reduce the number of long connections maintained by kube-apiserver, but I think that the Kubernetes registry is highly coupled with the upper-level business and reduces the amount of information available on the provider side. Homogenous other registration centers, such as etcdv3, Zookeeper do not provide different interfaces for Provider and Consumer.

[ Full content available at: https://github.com/apache/dubbo-go/issues/458 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org

[GitHub] [dubbo-go] AlexStocks commented on issue #458: Imp: change k8s labels

["AlexStocks (GitHub)" <gi...@apache.org>]

cc @sxllwx 

[ Full content available at: https://github.com/apache/dubbo-go/issues/458 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org