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.

Sign up for GitHub

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

Jump to bottom

Feature: Policy specification for L4 port mappings #202

Closed
3 tasks
tgraf opened this issue Nov 28, 2016 · 3 comments
Closed
3 tasks

Feature: Policy specification for L4 port mappings #202

tgraf opened this issue Nov 28, 2016 · 3 comments
Labels
kind/enhancement This would improve or streamline existing functionality.

Comments

@tgraf
Copy link
Member

tgraf commented Nov 28, 2016 •
edited

  • Allow specificy in policy what port mappings should occur, e.g. pod with label "role=backend" should map port 80 to port 8080.
  • Map policy spec to exiting BPF port mapping facilty
  • Tests
@tgraf tgraf added the kind/enhancement This would improve or streamline existing functionality. label Nov 28, 2016
@tgraf tgraf mentioned this issue Nov 28, 2016
Closed
@tgraf tgraf added this to the 0.9 milestone Mar 18, 2017
@danwent
Copy link
Contributor

danwent commented Apr 17, 2017

can you clarify this item?

@tgraf
Copy link
Member Author

tgraf commented Apr 23, 2017

can you clarify this item?

The main objective is to allow mapping a port, e.g. a pod listening on 8080 is mapped to port 80 without requiring to change the pod spec.

@tgraf tgraf modified the milestones: 0.10, 0.9 May 5, 2017
@tgraf tgraf removed this from the 0.10 milestone Jul 8, 2017
@tgraf
Copy link
Member Author

tgraf commented Jul 2, 2018

The best-practice is to use k8s services for this these days so this is no longer required

@tgraf tgraf closed this as completed Jul 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement This would improve or streamline existing functionality.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danwent @tgraf