-
Notifications
You must be signed in to change notification settings - Fork 673
[proxy] Add IPAM support #657
Comments
strawman:
|
@rade: For 2, any reason not to make this the default? It is the default for the router, correct? |
Also for 2, is there a way for the proxy to ask the router if IPAM is enabled? Adds a bit of complexity around what to do if the router is unavailable, but we need to handle that anyway. |
The reason to go for blank vars is consistency with how IPAM gets triggered in weave commands. i.e. IPAM is used iff the user did not supply any IPs. I don't mind supporting I don't think automatic IPAM should be the default; just like I'd leave out the 'figure out whether IPAM is enabled'. Can do that later if we feel like it. |
Personally, I'd expect |
The /status http request will have a line beginning 'Allocator'. I don't think there is any more direct route, but one could easily be added. |
I would not!
Then you are left with no way of using the proxy for ordinary (non-weave) containers. |
Since being able to use the proxy for both weave and non-weave containers is quite important, then option 1 is probably a better choice. So, let's make |
No description provided.
The text was updated successfully, but these errors were encountered: