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

CNI Plugins Should allow hairpin traffic #476

Open
caseydavenport opened this Issue Jun 13, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@caseydavenport
Copy link

caseydavenport commented Jun 13, 2017

Not 100% sure where this goes, but feels like CNI could be the right place to specify that plugins should support, but are not strictly required to support hairpin traffic (if/how each plugin does this will vary, so feels like it belongs in CNI rather than in the runtime).

Perhaps it should be an optional part of the spec, or a convention?

Context being this Kubernetes issue: kubernetes/kubernetes#45790

@cmluciano

This comment has been minimized.

Copy link

cmluciano commented Jun 13, 2017

Do any current plugins support hairpin mode?

@caseydavenport

This comment has been minimized.

Copy link
Author

caseydavenport commented Jun 13, 2017

@cmluciano at least the bridge plugin does: https://github.com/containernetworking/plugins/blob/master/plugins/main/bridge/bridge.go#L46

I think this issue is less strictly about "hairpin mode" than supporting traffic from a container that gets routed back to itself through whatever means that plugin deems appropriate.

@squeed

This comment has been minimized.

Copy link
Member

squeed commented Aug 9, 2017

We talked about this somewhat at the most recent meeting. It's clear that there are two aspects to this:

  1. The spec (or one of the related documents, e.g. conventions) should mention hairpin support
  2. The plugins should support hairpin traffic, especially as present in Kubernetes, Mesos, Rkt, etc.,

So there should be specific plugin issues + PRs as needed, and a spec change. In the context of this issue, we were thinking of adding a block to the conventions document that mentions hairpin mode and that plugins SHOULD support traffic being redirected back to the container.

Thoughts on specific wording?

@cmluciano

This comment has been minimized.

Copy link

cmluciano commented Aug 11, 2017

That sounds good to me @squeed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.