docs(en): add en operation doc

docs/_sidebar.md

@@ -69,6 +69,7 @@
         - [Zookeeper](en/component_specs/sequencer/zookeeper.md)
         - [MongoDB](en/component_specs/sequencer/mongo.md)
       - [Secret Store](en/component_specs/secret/common.md)
+  - [How to deploy and upgrade Layotto](en/operation/)
 - Design documents
   - [Actuator design doc](en/design/actuator/actuator-design-doc.md)
   - [Configuration API with Apollo](en/design/configuration/configuration-api-with-apollo.md)

docs/en/operation/README.md

@@ -0,0 +1,78 @@
+# How to deploy and upgrade Layotto
+
+## 1. Deploy Layotto
+
+There are some ways to deploy Layotto that you can find below.
+
+- Deploy Layotto from release binaries
+- Deploy using Docker
+- Deploy on Kubernetes
+
+### Deploy Layotto from release binaries
+
+To run, download or build the binary for your platform, then exec it. Refer to the [Quick start](en/start) guide.
+
+### Deploy using Docker
+
+You can run Layotto using the official Docker images.Currently include:
+
+- [layotto/layotto](https://hub.docker.com/repository/docker/layotto/layotto)
+- [layotto/layotto.arm64](https://hub.docker.com/repository/docker/layotto/layotto.arm64)
+
+It's not contain a `config.json` configuration file in the image, you can mount your own configuration file into the `/runtime/configs/` directory of the image. For example.
+
+```shell
+docker run -v "$(pwd)/configs/config.json:/runtime/configs/config.json" -d  -p 34904:34904 --name layotto layotto/layotto start
+```
+
+Of course, you can also run Layotto and other systems (such as Redis) at the same time via docker-compose. Refer to the [Quick start](en/start/state/start?id=step-1-deploy-redis-and-layotto)
+
+### Deploy on Kubernetes
+
+#### Option 1. Deploy via Istio
+
+If you are using Istio now, you can deploy the Sidecar via Istio.
+
+You can refer to [MOSN guide](https://mosn.io/docs/user-guide/start/istio/). Just replace the MOSN image in the tutorial with a Layotto image.
+
+#### Option 2. Other ways
+
+You can prepare your own image and k8s configuration file, then deploy Layotto via Kubernetes.
+
+We are working on the official Layotto image and the solution for deploying to Kubernetes using Helm, so feel free to join us to build it. More details in <https://github.com/mosn/layotto/issues/392>
+
+## 2.Toggle existing MOSN to Layotto for MOSN users
+
+Existing MOSN can be migrated directly to replace the MOSN image in the sidecar with Layotto image.
+
+Explanation:
+
+Layotto and MOSN are running in the same process, which can be understood as:
+
+> Layotto == MOSN + a special grpcFilter packaged together
+
+So.
+
+> replace MOSN with Layotto == replace MOSN with "MOSN + a special grpcFilter"
+
+There is no essential difference, just pay attention to the version, the versions Layotto and MOSN must correspond to each other.
+
+The previously released Layotto v0.3.0 corresponds to MOSN version v0.24.1
+
+## 3. How to upgrade Layotto
+
+There are two options to upgrade.
+
+- Upgrade sidecar container using k8s native solution
+
+- [Smooth upgrade with automatic migrate existing persistent connections](https://mosn.io/en/docs/concept/smooth-upgrade/)
+
+The advantage of smooth upgrade is that it can automatically migrate persistent connections, which can be seen in detail by clicking the above document.
+
+The options to achieve smooth upgrade are
+
+- The MOSN listens for SIGHUP, sends a SIGHUP signal to the MOSN process, and generates a new MOSN process via ForkExec.
+
+- Restarting a new MOSN process directly. Cross-container upgrades require Operator support.
+
+- [OpenKruise hot upgrades in-place](https://mosn.io/blog/posts/mosn-sidecarset-hotupgrade/)