Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revise DestinationPolicy #270

Closed
louiscryan opened this issue Dec 11, 2017 · 1 comment
Closed

Revise DestinationPolicy #270

louiscryan opened this issue Dec 11, 2017 · 1 comment
Assignees

Comments

@louiscryan
Copy link
Contributor

@rshriram @ZackButcher

DestinationPolicy is a decorator for a service declared in the service registry. Its responsibility is to describe common policy that should be used when talking to all endpoints within that service. As such it defines timeouts, retries, hashing of endpoints for affinity/sharding etc.

A DestinationPolicy can be defined to match a DNS wildcard prefix so that a single policy can be applied to many services within a cluster / namespace etc.

TODO:

  • Align file and schema organization with the above concept & cleanup docs / comments
  • How does policy inherit
  • Address how weighting, hashing and sharding are addressed within a service
  • Evaluate how to create named subsets within a service to simplify routing.
@geeknoid
Copy link
Contributor

Can we close this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants