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

Feature: Investigate simpler networking #23476

Closed
justinsb opened this issue Mar 25, 2016 · 5 comments
Closed

Feature: Investigate simpler networking #23476

justinsb opened this issue Mar 25, 2016 · 5 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@justinsb
Copy link
Member

The existing networking options seem to do full IPAM, but simple ip tunneling of CIDRs might be easier. We already allocate CIDRs in the API server, and nodes already have full visibility into other nodes's CIDRs.

Ubuntu’s Fan networking though seems to offer this: https://insights.ubuntu.com/2015/06/24/introducing-the-fan-simpler-container-networking/

We could also simply directly set up tunnels to every other node.

@justinsb justinsb added area/platform/aws kind/feature Categorizes issue or PR as related to a new feature. labels Mar 25, 2016
@justinsb justinsb added this to the v1.3 milestone Mar 25, 2016
@binarybana
Copy link

I think Calico looks particularly exciting too (though not sure how it compares with Fan), esp given that policies are already being demoed: https://www.projectcalico.org/calico-network-policy-comes-to-kubernetes/

@goltermann
Copy link
Contributor

Removing v1.3 milestone as this is a feature and won't make 1.3.

@goltermann goltermann modified the milestones: next-candidate, v1.3 Jun 13, 2016
@justinsb
Copy link
Member Author

I've actually made a lot of progress here, but most excitingly was able to separate it out into a separate controller thanks to #25614 . My WIP is here https://github.com/kopeio/kope-routing Once the 1.3 dust clears I hope to polish it up, but it isn't tied to a k8s release any more!

@justinsb justinsb self-assigned this Nov 15, 2016
@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2017
@caseydavenport
Copy link
Member

I believe this issue isn't relevant any more - there are a number of simple and easy to use networks available for k8s now.

/assign
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

7 participants