How are you planning on using kubeedge?

I've been looking for something like this for a long time (Currently our team uses Rancher although their product wasn't really meant for edge computing.) I'd love to hear how others in the community would like to use this so I can compile a list of use cases that kubeedge can support out of the box.

Thanks!

When passing Wasm function to the host as a callback, it's passed as an index in the table.
Wasm3 needs to provide an API to call such functions.

Motivation

Currently, our socket functions can handle ipv4 and ipv6 address. However, we would like to have a helper function to handle the url string. That is getaddrinfo.

Appendix

• https://man7.org/linux/man-pages/man3/getaddrinfo.3.html

https://www.usenix.org/conference/opml19/program

Prepare to read papers

Is your feature request related to a problem? Please describe.
I would like to set a custom and static interface name for the client to use with firewall rules

Describe the solution you'd like
An additional option here:

Would work great in my opinion.

**Describe alterna

nanovms/ops#525

What would you like to be added/modified:
currently, "superedge.io/edge-node": "enable" is used to identify an edge node. I recommend to add another label of "node-role.kubernetes.io/edge".
Why is this needed:
k8s use this kind of label for node roles, such as master, node, etc. It is more convenient for

It would be useful if Kuiper supported file-based rule and stream provisioning (i.e. importing) on startup. Currently rules and streams need to be created by someone using the client, or an application requesting creation via the Kuiper REST API.

Supporting file-based provisioning would allow someone to deploy Kuiper with a pre-defined set of streams and rules, removing the need for someone (or