Service Catalog on EdgeComputing with KubeEdge

[Zhang Qi]

Hi there,

I am from KubeEdge community(https://github.com/kubeedge/kubeedge). Now I am working on designing the mobility network capability expose with service catalog on 5G Edge scenario. However, there are somehting different in the Edge. 

Unlike the cloud scenario, some of the services can only be visited in edge to both end user and the cluster operator. So the service instance creation/bind operatios need to be performed in edge. But the service list operation can be operated in cloud.

As a summary, in the edge computing scenario, we may need to separate the service broker capabilities into two parties, one on Cloud to provide service/service plan management and one on Edge to provide instance/bind management. Also, this edge part need to be associated with the specified nodes which is able to provide such services(I am thinking that those nodes have some labels and the ServiceInstance object contain the same lables).

The second problem is, we can not create instances before the serivce bind and deployment creation since we have no idea where to create those instances（remember different edges provide different services）. So we may need to add such service instance requirement/binding information announcement in the deployment object. The such instance creation/binding operations can be down by the edgecore(edge version of kublet) once get the definition.

Above are some of my ideas, I am looking forward for your comments on such edge computing scenarios. Thanks