Yun Long

HTTP/2 is worth implementing.

As you can see in the architecture[1], the sidecar and agent cooperate to complete kinds of tasks. Sidecar would communicate with mesh control plane to get governance information. On one...

The `MeshDeployment` seems to be redundant after we support native Deployment. We plan to deprecate it in `v1.3.0`, delete it in `v1.4.0`.

Updated. There's a file to be noticed: operator/pkg/api/v1beta1/zz_generated.deepcopy.go is generated by controller-gen, but I still add the license manually. But the unit test is broken.. How about ignoring the zz...

Fixed a lot of little issues, please check them out.

EaseMesh also supports other languages besides Java/Spring by installing [EaseMesh-CoreDNS](https://github.com/megaease/easemesh/blob/main/docs/install.md#install-coredns) . And actually, we have supported mTLS[1] now without updating the document, which will be done soon. [1] https://github.com/megaease/easegress/blob/38eac8e335ece1cb3494c1f2033c017cf999338b/pkg/object/meshcontroller/spec/spec.go#L120

@madugula007 I've added a demo guide in README for https://github.com/megaease/easemesh-demo , please check it out.

Thanks for the warning, we'd like to consider removing it in the future.

1. Retrieval of deployment spec exmaple: `$ curl http://127.0.0.1:32202/apis/v2/mesh/services/order-mesh/deployment` which contains 3 major fields: 1. app: objest, deployment spec as k8s Deployment spec. 2. configMaps: array, the item is k8s...

Here are my opinions: 1. For now plain HTTP is acceptable for admin interfaces. 2. If we decide to support HTTPS or gRPC(like etcd3.x), it got more work. e.g. certificates...