Hi, gang!
I'm thinking about handling configs of both ServiceComb and other
frameworks(like Istio), then provide a unified solution for config
management, to support the hybrid solution scenario(like, user use
ServiceComb and Istio at the same time).
So the first thing to do is to make sure that the chassis configs have
an equivalent mapping of other frameworks. Currently, I'm testing the rate
limit configs between ServiceComb and Istio, it's working. I write a demo
about this at https://github.com/crystaldust/configcomb, receive a
chassis.yaml, read the Flowcontrol field, then convert it to Istio rate
limit rules and apply the rules in a kubernetes cluster. It should also
work the opposite way.
By doing so, it is possible to provide a unified solution for config
management, any ideas?
