Document deployment practice particularly wasm binary distribution

[codefromthecrypt]

What would you like to be added:

We should have documentation on how to configure the wasm plugin, including guidance in how to distribute the wasm.

Why is this needed:

Wasm binaries will start at several hundred KB, and in practice may be much larger. There are different approaches depending on size, for example, config maps, volumes, and http refs.

See #25 (comment) for some discussion

Completion requirements:

This enhancement requires the following artifacts:

• Design doc
• API change
• Docs update

The artifacts should be linked in subsequent comments.

[codefromthecrypt]

Configuration will change from "guestPath" to "guestURI" (or "guestUri"?) soon to allow file:// and https:// references such as @evacchi did recently for dapr's wasm plugin

[codefromthecrypt]

update: guestURI is done and accepts file:// http:// and https:// schemes (thanks @evacchi)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sanposhiho]

/remove-lifecycle stale
/lifecycle frozen