cloudnative

Transfering @NissesSenap's issue from ViaQ/loki-operator/issues/103

Today the operator only support aws and thus S3 object storage but on the other hand Loki have support for a number of none S3 storage solutions: https://grafana.com/docs/loki/latest/configuration/#storage_config

I know that this operator in a early stage but to make it easier for faster adoption it would be nice to support

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

功能上LGTM, 但现在每次get请求都要初始化一个 Git/Oss client，担心会有泄漏的问题，这块之后要考虑优化一下。

Originally posted by @wangyikewxgm in oam-dev/kubevela#2848 (review)

Now every time when we read addon files from GitHub or OSS, one client will be created. It causes resource waste and potential leak danger.
We should initialize an oss client and a github client. Use these two clie

What would you like to be added:
A Fault injection filter should provide configurable error injection capabilities, such as delay, error local reply. it is best to have more detailed routing-based configuration capabilities

Why is this needed:
Because this is the ability that is required in the testing phas

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.