Add Sentinel Envoy RLS server implementation #1139
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe what this PR does / why we need it
Add the
sentinel-cluster-server-envoy-rls
module, a Envoy RLS server implementation using Sentinel token server. See #666 (comment) for initial design proposal.Does this pull request fix one issue?
Resolves #666
Describe how you did it
EnvoyRlsRuleManager
: loadsEnvoyRlsRule
, convert to Sentinel cluster flow rules and apply toClusterFlowRuleManager
(indefault
namespace).EnvoySentinelRuleConverter
: convertEnvoyRlsRule
to clusterFlowRule
and generate a consistent and unique flow ID.SentinelEnvoyRlsServiceImpl
: the RLS gRPC service implementation, which will delegate rule checking toSimpleClusterFlowChecker
and assemble result for all descriptors.EnvoyRlsRuleDataSourceService
: for initializing the YAML file rule data source.SentinelEnvoyRlsServer
: the main entry of the RLS server.Describe how to verify it
Run the test cases and demo.
Special notes for reviews
NONE