[ https://issues.apache.org/jira/browse/SCB-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542665#comment-16542665 ]
ZhenJu commented on SCB-740: ---------------------------- OK, Willem, I'll send the idea to the mailing list > Unified config handler of ServiceComb and other micro service frameworks > ------------------------------------------------------------------------ > > Key: SCB-740 > URL: https://issues.apache.org/jira/browse/SCB-740 > Project: Apache ServiceComb > Issue Type: New Feature > Reporter: ZhenJu > Priority: Minor > > 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 a > 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? -- This message was sent by Atlassian JIRA (v7.6.3#76005)