Skaffold dev against canary deployments

- Skaffold does a very good job to facilitate application developments against a local k8s cluster with multi-modules support
- However, developing a feature against a local cluster usually faces the following problems
- Local machine may not be powerful enough to support a large application which contains a lot of services.
- submodules may not be up-to-date, users may end up accidentally working on something against a stale environment.
- It takes a lot of time to start all services.
- dummy data setup.
- A user may want to take the advantages of a remote cluster that provides the shared infrastructure while not contaminating it by deploying a canary to the cluster.
- The target service only provides grpc endpoints, the user can send a REST request against business gateway, it goes through several service then reaches to the target service behind a proxy.
- It should also be possible to share the canary with his co-worker for code-review :)
- With [k8s gateway api](https://gateway-api.sigs.k8s.io/) , skaffold could help creating proper traffic routing rule that can direct users request to their canary deployment, for example through special values for a header --