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!

Related to metering wasm3/wasm3#127 and being able to run a set number of instructions, I'd like to be able to serialize a paused interpreter's state and deserialize it to a new interpreter instance; very roughly,

const interp = new wasm3.Interpreter(module);
interp.interpretNInstructions(100);
const interpState = interp.serializeState();
const interp2 = wasm3.In

The MD file link you want to translate (must be in English)

https://github.com/WasmEdge/WasmEdge/blob/master/docs/book/en/src/kubernetes/container.md

Target language

zh: https://github.com/WasmEdge/WasmEdge/blob/master/docs/book/zh/src/kubernetes/container.md

ENHANCEMENT

1. Describe the enhancement you are requesting.
   Consider using Go errors group (golang.org/x/sync/errgroup) for handling routines in main functions of Mainflux services.

2. Indicate the importance of this enhancement to you (must-have, should-have, nice-to-have).
   This is a nice-to-have.

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

Prepare to read papers

nanovms/ops#525

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

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