cloudnative

https://github.com/heptiolabs/healthcheck

This will give us metric on healtcheck and more granularity on checks we want to have.

/cc @slim-bean @joe-elliott

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

1. the concept capability should merge with registry , the final name can be registry
2. we should have a default registry https://registry.kubevela.net
3. we should align the output format as below.

NAME           	REGISTRY  DESCRIPTION	  DEFINITION                    		APPLIES-TO         

What would you like to be added:
now, we have one integrate test example, add more

Why is this needed:

Is mushop validated against latest version of istio 1.10.x? The steps will defer from enabling kali/jageur etc which the docs is not updated.