[ipam] automatic IP assignment in combination with Kubernetes

[slintes]

Hi,

as discussed via mail with Bryan it would be nice to have automatic IP assignment when using weave in combination with Kubernetes, like it is done here: https://github.com/errordeveloper/weave-demos/tree/master/poseidon. The current configuration (writing configuration files with cloud config for each cluster node) is not scalable.
A nice option for providing the basic configuration and coordinating individual configurations of the cluster nodes would be using etcd.

This is related to #22, but another usecase.

Kind regards, Marc

[squaremo]

With regard to how this relates to #22, @errordeveloper said:

Basically what we need for each new host that comes up is a subnet for docker bridge. This subnet
has to be assigned before docker starts and before weave starts. Although, we actually are gonna
have the hostname or IP of one of the weave routers, so perhaps we could call on some API that
weave might implement and it would be as simple as "gimme next CIDR for a Kubernetes host", where > 'Kubernetes' is like a policy of a kind.

[slintes]

Hi. Am I right that the latest weave release with IPAM is not useful for this issue? Just wanted to upgrade and give it a try, but I saw that @errordeveloper also didn't update his "poseidon" example (yet?).

[errordeveloper]

@slintes I am planning to work on this after kubernetes/kubernetes#9646 is merged. Right now, there is no way to tell Kubernetes what IP we allocated for a pod, basically.

[slintes]

ok, thx!

[rade]

@paulbellamy @errordeveloper does #1199 address this issue?

[errordeveloper]

I am quite sure it does, Matthias. Please close this one.

On Fri, 4 Sep 2015 08:00 Matthias Radestock notifications@github.com
wrote:

@paulbellamy https://github.com/paulbellamy @errordeveloper
https://github.com/errordeveloper does #1199
#1199 address this issue?

—
Reply to this email directly or view it on GitHub
#212 (comment).