8000 CNI plugin assigns an IP to the bridge by itself by bboreham · Pull Request #2471 · weaveworks/weave · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Jun 20, 2024. It is now read-only.

CNI plugin assigns an IP to the bridge by itself #2471

Merged
merged 1 commit into from
Aug 10, 2016
Merged

CNI plugin assigns an IP to the bridge by itself #2471

merged 1 commit into from
Aug 10, 2016

Conversation

bboreham
Copy link
Contributor
@bboreham bboreham commented Aug 8, 2016

No need to call weave expose before use. (see below) This simplifies set-up for Kubernetes, etc.

It only does if the config doesn't specify any routes or gateway, which may be too restrictive, but I guess we can wait for customer feedback.

CC @abuehrle for review of doc change

@bboreham bboreham added this to the 1.6.1 milestone Aug 8, 2016
No need to call `weave expose` before use.
@abuehrle
Copy link
Contributor
abuehrle commented Aug 9, 2016

LGTM

@awh awh merged commit 96f2eb3 into 1.6 Aug 10, 2016
@awh awh deleted the cni-bridge-ip branch August 10, 2016 10:49
@bboreham
Copy link
Contributor Author

We do still need the fuller weave expose in at least one case:

When a pod contacts a service on another node, it will start the conversation sending to the service address, which will be DNAT-ted to a node's real IP address. When the packet arrives at that host, it will arrive on the underlay network interface, and be dropped as a martian.

So, we need the masquerade rules on the source host, so when the packet leaves the Weave network it changes its return address to the underlay IP address of the source host.

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

Successfully merging this pull request may close these issues.

3 participants
0