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

Use traffic controller to manage TrafficGate and Pipeline #20

Closed
xxx7xxxx opened this issue Jun 15, 2021 · 0 comments · Fixed by #55
Closed

Use traffic controller to manage TrafficGate and Pipeline #20

xxx7xxxx opened this issue Jun 15, 2021 · 0 comments · Fixed by #55
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@xxx7xxxx
Copy link
Contributor

Background

Currently, the architecture shows below.

image

It has some problems:

  • TrafficGate and Pipeline have been used by multiple sources such as static config, Mesh, etc.
  • No namespaces to separate.
  • It's hard to do global scheduling for them.

Proposal

So we decide to use a dedicated controller to manage them. Here's the new architecture:

image

We got the benefits:

  • Supervisor is much cleaner as managing controllers only
  • More extensibility by using one core(traffic controller) and external resource users(default traffic, mesh, faas, etc).
  • Data and statistics can be merged/calculated better with namespaces.
@xxx7xxxx xxx7xxxx self-assigned this Jun 15, 2021
@benja-wu benja-wu pinned this issue Jun 15, 2021
@benja-wu benja-wu added the enhancement New feature or request label Jun 16, 2021
@benja-wu benja-wu added this to the v1.0.1 milestone Jun 17, 2021
@zhao-kun zhao-kun added this to In progress in Easegress Project Jun 17, 2021
Easegress Project automation moved this from In progress to Done Jun 24, 2021
@benja-wu benja-wu unpinned this issue Jun 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

2 participants