sofastack / sofa-mesh Goto Github PK

as sofa-mosn base on version 0.4.0 of go-control-plane now, forced go-control-plane on sofa-mesh to same version

目前用zookeeper做命名服务（用Nacos做命名服务也会面临同样疑问）迁移到sofa-mesh，nacos（或zk）的数据需要同步到etcd中吗？还是nacos已经提供了成熟的client可以在sofa-mesh直接使用？ 大规模注册中心对zk的客户端稳定性要求很高，现在go zk client（地址：https://github.com/samuel/go-zookeeper ）只是个demo，直接使用可能会严重影响稳定性。

ISTIO use envoy a data plane sidecar by default, sofa-mesh is designed to use sofa-mosn instead.
We should provider the samples, installation scripts, build script to use sofa-mosn.

如上，构建的时候发现缺istio.io/istio的包，源码里面没有上传

currentListenerEntry was nil case ListenerTypeX

Is there metrics to prometheus when service is dubbo rpc

Create sofa consumer and provider sample application to demonstrate the x-protocol e2e cases

For epic #5

This new adapter work together with the "kube" platform adapter, it will subdivide k8s service by its interface, so that labels can be applied on individual interface.

Is there any plan to support the gRPC protocol?

Describe the bug
A clear and concise description of what the bug is.

Expected behavior
A clear and concise description of what you expected to happen.

Steps to reproduce the bug
Steps to reproduce the behavior.

Version
What version of istio and Kubernetes are you using? Use istioctl version and kubectl version

Is Istio Auth enabled or not?
Did you install the stable istio.yaml, istio-auth.yaml.... or if using the Helm chart please provide full command line input.

Environment
Which environment, cloud vendor, OS, etc are you using?

Cluster state
If you're running on Kubernetes, consider following the
instructions
to generate "istio-dump.tar.gz", then attach it here by dragging and dropping
the file onto this issue.

In this issue I will add sofa-mosn introduction to sofa-mesh's docs

The ci pipeline is not working after fork from istio upstream.

DNS is the standard way to discovery services in the cloud native environment, traditional RPC frameworks, were designed for SOA architecture, did not follow the 12 factor design pattern and not well supported on kubernetes, for example DUBBO and SOFA, they allow multiple services co-located on a single workload.

This feature will use sub domain support of CoreDNS to represent different services, so that they can be discovered by kubernetes DNS.
A register agent component will be created to pull service information from work loads and discovery systems.
A controller component is created to watch k8 service and register agent to create mapping between service and cluster ip and actively push service and sub domain to core dns.

PILOT provider adapter interfaces to integrate with external service discovery systems, such as consul and eureka, it can be extended to support zookeeper and etcd. actually we implement zk support for SOFA. But it is designed to integrate workloads on VM and baremetal deployments, not to bring them on to kubernetes.

请教下数据同步模块是哪块代码？

For epic #5
Register agent is co-deployed with the service application in the same container. it providers a unified way to expose the service interfaces of the underline service application.

Is your feature request related to a problem? Please describe.
is a dead project?

https://github.com/alipay/sofa-mesh/blob/x-protocol-quickstart/samples/e2e-dubbo/platform/kube/README.md
按实例流程执行到这一步
helm install install/kubernetes/helm/istio --name istio --namespace istio-system
总是报错
Error: customresourcedefinitions.apiextensions.k8s.io "gateways.networking.istio.io" already exists

follow istio 1.0.1 and upgrade go-control-plane version

the [pilot/pkg/networking/plugin/mixer.go] file ( https://github.com/alipay/sofa-mesh/blob/master/pilot/pkg/networking/plugin/mixer/mixer.go ) has error because of too many arguments in call to addServiceConfig.

the compile  error info :
 pilot\pkg\networking\plugin\mixer\mixer.go:178:45: too many arguments in call to addServiceConfig
	have (*model.Proxy, map[string]*types.Struct, *client.ServiceConfig)
	want (map[string]*types.Struct, *client.ServiceConfig)
pilot\pkg\networking\plugin\mixer\mixer.go:251:46: too many arguments in call to addServiceConfig
	have (*model.Proxy, map[string]*types.Struct, *client.ServiceConfig)
	want (map[string]*types.Struct, *client.ServiceConfig)
pilot\pkg\networking\plugin\mixer\mixer.go:260:48: too many arguments in call to addServiceConfig
	have (*model.Proxy, map[string]*types.Struct, *client.ServiceConfig)
	want (map[string]*types.Struct, *client.ServiceConfig)
pilot\pkg\networking\plugin\mixer\mixer.go:269:48: too many arguments in call to addServiceConfig
	have (*model.Proxy, map[string]*types.Struct, *client.ServiceConfig)
	want (map[string]*types.Struct, *client.ServiceConfig)
pilot\pkg\networking\plugin\mixer\mixer.go:355:17: undefined: node

for example:
the subprotocol of port name "x-dubbo-user" would be "dubbo" before, now it will be "x-dubbo"

follow istio 1.1.4 and upgrade go-control-plane version

Describe the bug
There is no SidecarOutboundListener for dubbo service .

https://github.com/sofastack/sofa-mesh/blob/master/pilot/pkg/networking/core/v1alpha3/listener.go#L907

Maybe this part of the code was missing when merging it.

Expected behavior
SidecarOutboundListener for dubbo service should exist in consumer sidecar

Version
sofa-mesh v0.5.0-rc1 or master

Environment
CentOS7/RHEL7

this two annotation can be used to configure which ports to redirect to sidecar in outbound

Create a register agent to query service info from sofa boot applications

各位大神，master分支的e2e-dubbo实例consumer调用provider总是报超时，已经跑不通了，能帮忙解释一下吗？

Describe the feature request
{{
when i run the demo of X-protocol,i could not find the fill install/kubernetes/helm/istio/templates/crds.yaml
}}

Describe alternatives you've considered
{{
if the file changed site or change the name?
could fix the file ,thanks.
i want use this demo seeing the internal transmission,thanks.
}}

Additional context
{{ Add any other context about the feature request here }}

For epic #5

RPC Service Controller watch RPC Service customer resource through Kubernetes API server, then fetch service interface from the co-deployed register agent and use these informations to generate and update DNS entry for RPC Service.

这个工程没人维护了吗？