Skip to content

[new feature] Multi-port service routing & port selection flexibility #26

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

Closed
foxish opened this issue Aug 2, 2023 · 1 comment
Closed
Labels

Comments

@foxish
Copy link
Member

foxish commented Aug 2, 2023

New feature or functionality
What would you like Signadot to do?

Add more flexibility to the routing:

  1. Ability to intercept from / route to specific ports on a baseline / fork workload when there are multiple listening ports
  2. Ability to fork workloads that aren't going to participate in routing (opting out of routing entirely)

Additional considerations
Anything in particular to think about regarding this new feature?

@foxish foxish added the platform label Aug 2, 2023
@foxish foxish moved this to Under Consideration in Signadot Public Roadmap Aug 2, 2023
@foxish foxish moved this from Under Consideration to In Progress in Signadot Public Roadmap Aug 14, 2023
@foxish foxish changed the title [new feature] Routing port selection flexibility [new feature] Multi-port routing & port selection flexibility Sep 21, 2023
@foxish foxish changed the title [new feature] Multi-port routing & port selection flexibility [new feature] Multi-port service routing & port selection flexibility Sep 21, 2023
@foxish
Copy link
Member Author

foxish commented Oct 12, 2023

Addressed in v0.14.0 released on 2023-10-12.

@foxish foxish closed this as completed Oct 12, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in Signadot Public Roadmap Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

1 participant