Use device API both on cloud and edge

[fisherxu]

What would you like to be added/modified:
Now we have defined device API in the cloud side, but the edgeside(edgecore and mapper) still don't use the API, we should refact edgeside and use same API on cloud and edge to reduce complexity.

[luogangyi]

how edgeside use api? directly call K8S api or through some proxy tunnel?

[fisherxu]

Support list-watch from edgecore for applications is in our roadmap, xref: #1758, we need to add proxy tunnel to support list-watch from edgecore, then can call K8S api.

And now the device api in edge has no namespace, it's not k8s style.

[luogangyi]

seem great！ current device management code is too complicated and hard to maintain

[backbencher00]

@fisherxu hi, I'm interested in working on this project as part of community bridge. I also applied on the website for the same. I would he happy to discuss more about the project and provide more information. Can you please help me getting started? :)

[kkBill]

Based on the discussion in previous community meetings, my tentative proposal is as follows: https://github.com/kkBill/kubeedge/blob/deviceapi%40edge/docs/proposals/deviceapi-edge-design.md, please have a look and let us discuss further. @fisherxu @luogangyi

[stale]

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

[stale]

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗