add support for `ips` in ipam config #3754

nonsense · 2020-01-16T12:12:41Z

This PR is adding an additional field in the IPAM config for Weave - ips.

It allows for specifying an IP address through the CNI plugin, similar to weave attach and claim that IP.

I am not sure if it makes sense to configure also checkAlive or to set it to true at all times - currently it is set to false.
Since the IPAM configuration is specific to each plugin, I think this is allowed per the CNI spec. I am not sure if the choice for ips type is right though - this type is used in the Result, but it seemed appropriate for the input values of the IPAM as well.

TODO:

fix 880_cni_plugin_ip_address_assignment_test.sh.sh tests to test new functionality

bboreham · 2020-01-21T10:34:53Z

Thanks for the PR! Would you consider adding a test, e.g. extending https://github.com/weaveworks/weave/blob/master/test/830_cni_plugin_test.sh

(the integration tests at CircleCI always fail for 3rd-party branches, but I've pushed your branch to this repo so they will run this time)

bboreham

Some points to consider.

plugin/ipam/cni.go

bboreham · 2020-01-21T10:42:56Z

plugin/ipam/cni.go

@@ -37,7 +38,15 @@ func (i *Ipam) Allocate(args *skel.CmdArgs) (types.Result, error) {
 	}
 	var ipnet *net.IPNet

-	if conf.Subnet == "" {
+	if len(conf.IPs) == 1 {


What happens when 2 or more IPs are supplied?

I am not sure how we can assign multiple IP addresses to the same interface we pass as part of RuntimeConf, when calling AddNetworkList.

plugin/ipam/cni.go

bboreham · 2020-01-21T10:52:07Z

I am not sure if it makes sense to configure also checkAlive

In a Kubernetes context it won't make any difference - that parameter is only used when Weave Net is configured to talk to Docker.

nonsense · 2020-01-22T15:42:01Z

@bboreham thank you for the review. I will make sure I add a test and address all your comments and questions in the coming days!

bboreham · 2020-02-26T11:44:33Z

Thanks for the test; there appear to be a couple of points still outstanding from my first review - could you respond to those?

nonsense · 2020-02-26T12:55:52Z

@bboreham sorry for the delay :( I am trying to prioritise this alongside other work. I will definitely address the rest of the issues, and ping you, when this is ready for another review!

bboreham · 2020-02-26T14:49:31Z

Hey, no apology required! I've re-pushed the branch so your new test should run in CI.

nonsense · 2020-05-07T18:54:42Z

plugin/ipam/cni.go

-		ipnet, err = i.weave.AllocateIP(containerID, false)
+	var ipconfigs []*current.IPConfig
+
+	if len(conf.IPs) > 0 {


@bboreham I am a bit confused with how to support >1 IPs passed to the CNI via a NetworkConfigList, since the signature of AddNetworkList is:

func (c *CNIConfig) AddNetworkList(ctx context.Context, list *NetworkConfigList, rt *RuntimeConf) (types.Result, error) {

and RuntimeConf includes:

type RuntimeConf struct { ContainerID string NetNS string IfName string ...

Can a given interface (i.e. eth1) have multiple IP addresses? I am assuming we set IfName to eth1 for example.

I hope that makes sense.

Yes, an interface can have many IP addresses. These days one IPv4 and one IPv6 is quite common (though not in Weave Net).

What you did is OK, though the Weave Net CNI plugin will currently only use the first address:

weave/plugin/net/cni.go

Lines 85 to 86 in b04217d

// Only expecting one address

ip := result.IPs[0]

bboreham

Thanks for this; sorry I didn't get back to you. Some small notes below.

I was going to ask about handling IPs in DEL, but it makes me realise that DEL is already bugged for the case that ADD is called twice (for eth0 and eth1, say), because it will release all IPs on the first DEL. I guess that should at least be filed as an issue to be addressed later.

plugin/ipam/cni.go

bboreham · 2021-01-18T12:44:19Z

plugin/ipam/cni.go

-		ipnet, err = i.weave.AllocateIP(containerID, false)
+	var ipconfigs []*current.IPConfig
+
+	if len(conf.IPs) > 0 {


Yes, an interface can have many IP addresses. These days one IPv4 and one IPv6 is quite common (though not in Weave Net).

What you did is OK, though the Weave Net CNI plugin will currently only use the first address:

weave/plugin/net/cni.go

Lines 85 to 86 in b04217d

// Only expecting one address

ip := result.IPs[0]

nonsense · 2021-01-18T14:58:07Z

Thanks for this; sorry I didn't get back to you. Some small notes below.

No worries!

I think I addressed all comments. Let me know if you think this PR should include anything else.

I'd be very happy if this gets into Weave at some point, so that we can stop using a fork on Testground!

bboreham · 2021-01-18T15:14:44Z

It looks like your test/831_cni_plugin_ip_address_assignment_test.sh is identical to the existing test 830; it should exercise the new feature.

nonsense · 2021-01-18T17:47:55Z

It looks like your test/831_cni_plugin_ip_address_assignment_test.sh is identical to the existing test 830; it should exercise the new feature.

Any chance we can allow this PR to run these tests on CI? I didn't manage to get the test setup to run locally last time, and it seems like it will be fairly easy to update the code and test on CI.

bboreham · 2021-01-19T18:30:30Z

We have no automated system to allow 3rd-party PRs access to the secrets; what I generally do is manually pull your branch and push it to the weaveworks/weave repo.

Note that your test doesn't need to duplicate all the twists and turns of test 830; it just needs to make one or two calls with the IPs set and check the result.

The tests do assume they can ssh into another host where Docker is running with open TCP socket.
To run completely locally you can edit out that assumption:

diff --git test/830_cni_plugin_test.sh test/830_cni_plugin_test.sh
index e53e988c..a8d93cc0 100755
--- test/830_cni_plugin_test.sh
+++ test/830_cni_plugin_test.sh
@@ -131,9 +131,9 @@ assert_raises "exec_on $HOST1 c1 $PING $C3IP"
 # CH0_HAIRPIN=$($SSH $HOST1 cat /sys/devices/virtual/net/weave/brif/$CH0_PEER/hairpin_mode)
 # assert_raises "[ $CH0_HAIRPIN == 1 ]"
 #
-assert "$SSH $HOST1 cat /sys/devices/virtual/net/weave/brif/vethwepl${CH0:0:7}/hairpin_mode" "1"
-assert "$SSH $HOST1 cat /sys/devices/virtual/net/weave/brif/vethwepl${CH1:0:7}/hairpin_mode" "0"
-assert "$SSH $HOST1 cat /sys/devices/virtual/net/weave/brif/vethwepl${CH2:0:7}/hairpin_mode" "1"
+assert "cat /sys/devices/virtual/net/weave/brif/vethwepl${CH0:0:7}/hairpin_mode" "1"
+assert "cat /sys/devices/virtual/net/weave/brif/vethwepl${CH1:0:7}/hairpin_mode" "0"
+assert "cat /sys/devices/virtual/net/weave/brif/vethwepl${CH2:0:7}/hairpin_mode" "1"
 
 
 
@@ -141,13 +141,13 @@ assert "$SSH $HOST1 cat /sys/devices/virtual/net/weave/brif/vethwepl${CH2:0:7}/h
 stop_weave_on $HOST1
 
 # Ensure no warning is printed to the standard error:
-ACTUAL_OUTPUT=$(CHECKPOINT_DISABLE="$CHECKPOINT_DISABLE" DOCKER_HOST=tcp://$HOST1:$DOCKER_PORT $WEAVE launch 2>&1)
-EXPECTED_OUTPUT=$($SSH $HOST1 docker inspect --format="{{.Id}}" weave)
+ACTUAL_OUTPUT=$(CHECKPOINT_DISABLE="$CHECKPOINT_DISABLE" $WEAVE launch 2>&1)
+EXPECTED_OUTPUT=$(docker inspect --format="{{.Id}}" weave)
 
 assert_raises "[ $EXPECTED_OUTPUT == $ACTUAL_OUTPUT ]"
 
-assert "$SSH $HOST1 \"curl -s -X GET 127.0.0.1:6784/ip/$C1 | grep -o -E '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'\"" "$C1IP"
-assert "$SSH $HOST1 \"curl -s -X GET 127.0.0.1:6784/ip/$C3 | grep -o -E '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'\"" "$C3IP"
+assert "curl -s -X GET 127.0.0.1:6784/ip/$C1 | grep -o -E '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'" "$C1IP"
+assert "curl -s -X GET 127.0.0.1:6784/ip/$C3 | grep -o -E '[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}'" "$C3IP"
 
 
 end_suite
diff --git test/config.sh test/config.sh
index 3b599ffa..76483877 100644
--- test/config.sh
+++ test/config.sh
@@ -101,7 +101,7 @@ run_on() {
     host=$1
     shift 1
     [ -z "$DEBUG" ] || greyly echo "Running on $host: $@" >&2
-    remote $host $SSH $host "$@"
+    "$@"
 }
 
 get_command_output_on() {
@@ -115,7 +115,7 @@ docker_on() {
     host=$1
     shift 1
     [ -z "$DEBUG" ] || greyly echo "Docker on $host:$DOCKER_PORT: $@" >&2
-    docker -H tcp://$host:$DOCKER_PORT "$@"
+    docker "$@"
 }
 
 docker_api_on() {
@@ -136,7 +136,7 @@ weave_on() {
     host=$1
     shift 1
     [ -z "$DEBUG" ] || greyly echo "Weave on $host:$DOCKER_PORT: $@" >&2
-    CHECKPOINT_DISABLE="$CHECKPOINT_DISABLE" DOCKER_HOST=tcp://$host:$DOCKER_PORT $WEAVE "$@"
+    CHECKPOINT_DISABLE="$CHECKPOINT_DISABLE" $WEAVE "$@"
 }
 
 stop_weave_on() {
@@ -151,7 +151,7 @@ exec_on() {
     host=$1
     container=$2
     shift 2
-    docker -H tcp://$host:$DOCKER_PORT exec $container "$@"
+    docker exec $container "$@"
 }
 
 # Look through 'docker run' args and try to make the hostname match the name

Then the run looks a little untidy because the CNI results are going to stdout, but you can see it worked:

$ HOSTS=localhost ./test/830_cni_plugin_test.sh -v
Cleaning up on localhost: removing all containers and resetting weave
Docker on localhost:2375: rm -f -v 8adc08a80d77 097012a50dad 5bb8f188cfbf 87388592180a 2505ab650754 00ae9ed80765 fa9597b14449 2dbfc8cf44e3 e8c6965ffe8f
Running on localhost: sudo rm -f /opt/cni/bin/weave-plugin-latest /opt/cni/bin/weave-net /opt/cni/bin/weave-ipam /etc/cni/net.d/10-weave.conflist
Test CNI plugin
Running on localhost: sudo mkdir -p /opt/cni/bin
Weave on localhost:2375: setup-cni
Weave on localhost:2375: launch
7ddcd31e8a63473b58d83c09a8918c5bbc0feee7f64040e9a6700631257dbba2
Docker on localhost:2375: run --net=none --name=c0 -dt alpine /bin/sh
Docker on localhost:2375: run --net=none --privileged --name=c1 -dt alpine /bin/sh
Docker on localhost:2375: run --net=none --name=c2 -dt alpine /bin/sh
Docker on localhost:2375: run --net=none --name=ch0 -dt alpine /bin/sh
Docker on localhost:2375: run --net=none --name=ch1 -dt alpine /bin/sh
Docker on localhost:2375: run --net=none --name=ch2 -dt alpine /bin/sh
net.ipv4.conf.all.arp_accept = 1
Docker on localhost:2375: inspect -f {{.State.Pid}} c0
Docker on localhost:2375: inspect -f {{.Id}} c0
Running on localhost: sudo CNI_COMMAND=ADD CNI_CONTAINERID=84f55149129a23980253b5b7e34ca7070be7611d24e264d6178461848a0d9b17 CNI_IFNAME=eth0 CNI_NETNS=/proc/3320277/ns/net CNI_PATH=/opt/cni/bin /opt/cni/bin/weave-net
{
    "ip4": {
        "ip": "10.32.0.1/12",
        "gateway": "10.32.0.2"
    },
    "dns": {}
}Docker on localhost:2375: inspect -f {{.State.Pid}} c1
Docker on localhost:2375: inspect -f {{.Id}} c1
Running on localhost: sudo CNI_COMMAND=ADD CNI_CONTAINERID=d36df517afbe134c6b3b16a54c5bee33482825f939b5168fb560d289a8a60fdd CNI_IFNAME=eth0 CNI_NETNS=/proc/3320334/ns/net CNI_PATH=/opt/cni/bin /opt/cni/bin/weave-net
{
    "ip4": {
        "ip": "10.32.0.3/12",
        "gateway": "10.32.0.2"
    },
    "dns": {}
}Docker on localhost:2375: inspect -f {{.State.Pid}} c2
Docker on localhost:2375: inspect -f {{.Id}} c2
Running on localhost: sudo CNI_COMMAND=ADD CNI_CONTAINERID=2421f061c5d7cd8c1165affa9cd6de1a4934cad2e5a30aab47381044a10083bf CNI_IFNAME=eth0 CNI_NETNS=/proc/3320402/ns/net CNI_PATH=/opt/cni/bin /opt/cni/bin/weave-net
{
    "ips": [
        {
            "version": "4",
            "address": "10.32.0.4/12"
        }
    ],
    "routes": [
        {
            "dst": "10.32.0.0/12"
        }
    ],
    "dns": {}
}Docker on localhost:2375: inspect -f {{.State.Pid}} ch0
Docker on localhost:2375: inspect -f {{.Id}} ch0
Running on localhost: sudo CNI_COMMAND=ADD CNI_CONTAINERID=2cb4dba09753e6169a7f2abdf96ebefadad83cabb4e462c45fd5b931cbee9a05 CNI_IFNAME=eth0 CNI_NETNS=/proc/3320463/ns/net CNI_PATH=/opt/cni/bin /opt/cni/bin/weave-net
{
    "ip4": {
        "ip": "10.32.0.5/12",
        "gateway": "10.32.0.2"
    },
    "dns": {}
}Docker on localhost:2375: inspect -f {{.State.Pid}} ch1
Docker on localhost:2375: inspect -f {{.Id}} ch1
Running on localhost: sudo CNI_COMMAND=ADD CNI_CONTAINERID=86bc28f08ca70653c81bb2b86c598999a0f2fddf062ad76af5696df0ce404974 CNI_IFNAME=eth0 CNI_NETNS=/proc/3320520/ns/net CNI_PATH=/opt/cni/bin /opt/cni/bin/weave-net
{
    "ip4": {
        "ip": "10.32.0.6/12",
        "gateway": "10.32.0.2"
    },
    "dns": {}
}Docker on localhost:2375: inspect -f {{.State.Pid}} ch2
Docker on localhost:2375: inspect -f {{.Id}} ch2
Running on localhost: sudo CNI_COMMAND=ADD CNI_CONTAINERID=a0f9b4b1a3580cbb6025cb48d549a067803c1f57f7df7b45a32f9f4d770a1e1c CNI_IFNAME=eth0 CNI_NETNS=/proc/3320577/ns/net CNI_PATH=/opt/cni/bin /opt/cni/bin/weave-net
{
    "ip4": {
        "ip": "10.32.0.7/12",
        "gateway": "10.32.0.2"
    },
    "dns": {}
}Weave on localhost:2375: ps c0
Weave on localhost:2375: ps c1
Weave on localhost:2375: ps c2
Weave on localhost:2375: ps weave:expose
.......Docker on localhost:2375: rm -f c2
c2
Docker on localhost:2375: run --net=none --name=c3 -dt alpine /bin/sh
Docker on localhost:2375: inspect -f {{.State.Pid}} c3
Docker on localhost:2375: inspect -f {{.Id}} c3
Running on localhost: sudo CNI_COMMAND=ADD CNI_CONTAINERID=e21ed597f48ba3aa3f323fea344621d594c502c84f341dadecdb8966811d52b6 CNI_IFNAME=eth0 CNI_NETNS=/proc/3321708/ns/net CNI_PATH=/opt/cni/bin /opt/cni/bin/weave-net
{
    "ip4": {
        "ip": "10.32.0.8/12",
        "gateway": "10.32.0.2"
    },
    "dns": {}
}Weave on localhost:2375: ps c3
..........
all 17 tests passed in 14.710s.```

Also note the first thing each test suite does is `rm -f` every container on the host.

nonsense · 2021-01-19T18:36:49Z

@bboreham OK, thanks for the pointers, will do that and ping you when ready.

nonsense · 2021-01-25T15:52:40Z

@bboreham thanks to the tips on how to run tests locally, I am able to run the test suite now! I started adding a test for this functionality, but when running HOSTS=localhost ./test/880_cni_plugin_ip_address_assignment_test.sh -v, it errors with:

Running on localhost: sudo CNI_COMMAND=ADD CNI_CONTAINERID=d682738721b9f73e39482be6486164bb3a42d4b7d219fe1d5d91bf8d26a8ae18 CNI_IFNAME=eth0 CNI_NETNS=/proc/145243/ns/net CNI_PATH=/opt/cni/bin /opt/cni/bin/weave-net
{
    "code": 100,
    "msg": "unable to allocate IP address for bridge: 400 Bad Request: Unable to claim: address 10.32.1.30/32 is already owned by d682738721b9f73e39482be6486164bb3a42d4b7d219fe1d5d91bf8d26a8ae18\n"
}

Not sure why we are not able to claim that address. I checked the following places:

docker logs weave doesn't explain the error
c0, c1 and c2 have only lo iface.
weave status ipam shows all IPs are available:

➜  weave git:(3d2524c6) ✗ ./weave status ipam
32:7d:23:67:8a:ff(ip-172-31-6-138)     1048576 IPs (100.0% of total) (1 active)

I also rebased the PR onto latest master as it was quite outdated.

bboreham · 2021-01-25T16:57:05Z

weave status ipam shows all IPs are available:

It shows that all but 1 are available ("1 active").

weave ps should tell you where that IP is in use, or curl 127.0.0.1:6784/ip

nonsense · 2021-01-25T17:59:09Z

ipam/claim.go

+	case c.ident == "weave:expose":
+		alloc.debugln("Ignoring weave:expose")
+		c.sendResult(nil)


@bboreham I am not entirely sure what's going on here. Without this case that ignores weave:expose, this is what I see in the weave logs:

DEBU: 2021/01/25 17:56:56.533494 [http] PUT /ip/99cb8ae4fe35aa7992bc1ae439fcd07bc464b9ccc846ec6140d3860665adedaf/10.32.1.30/8 INFO: 2021/01/25 17:56:56.533603 Assuming quorum size of 1 DEBU: 2021/01/25 17:56:56.533612 [allocator 32:7d:23:67:8a:ff] Paxos proposing DEBU: 2021/01/25 17:56:56.533644 [allocator 32:7d:23:67:8a:ff]: Paxos consensus: [32:7d:23:67:8a:ff] DEBU: 2021/01/25 17:56:56.536546 [allocator 32:7d:23:67:8a:ff]: Claimed 10.32.1.30/8 for 99cb8ae4fe35aa7992bc1ae439fcd07bc464b9ccc846ec6140d3860665adedaf DEBU: 2021/01/25 17:56:56.537963 [ring 32:7d:23:67:8a:ff]: ReportFree token=10.32.0.0 peer=32:7d:23:67:8a:ff version=1 DEBU: 2021/01/25 17:56:56.538721 [http] PUT /ip/weave:expose/10.32.1.30/8 WARN: 2021/01/25 17:56:56.540951 [allocator]: Unable to claim: address 10.32.1.30/8 is already owned by 99cb8ae4fe35aa7992bc1ae439fcd07bc464b9ccc846ec6140d3860665adedaf ; i am weave:expose

I added the i am weave:expose part, which corresponds to c.ident. I am not sure why func (c* claim) Try is called with weave:expose for ident, after an IP has been allocated to the container.

Looks like PUT /ip/weave:expose/10.32.1.30/8 is entering a check for the claim on the IP, and then complains that a container owns the IP already.

nonsense · 2021-01-25T18:04:16Z

I've added a test and it is passing locally. @bboreham could you also trigger the remote CI, just to make sure that I haven't messed up the setup phase while testing locally?

The test creates 3 containers with static IPs, and makes sure that these containers can see each other, and that they can't access the open internet.

For some reason weave:expose is calling claim.Try() (discussed above in a comment), and I imagine there is a proper way to handle that case, so this might need adjustment.

bboreham · 2021-01-25T18:16:33Z

I think your main problem is you left in all sorts of logic from the other test, including BRIP=$(container_ip $HOST1 weave:expose) which is allocating an address for the bridge.

Strip it down to just what you mean to test.

bboreham · 2021-01-25T18:20:03Z

Sorry, changed my mind, that line wouldn't do a PUT with a specific IP.

I do recommend you strip down the test, but you'd need to find out where that PUT is coming from.

bboreham · 2021-01-26T11:50:50Z

Could you check if you have a pre-existing address on the weave bridge?

Like ip addr show dev weave.

You may want to do weave reset --force before running the test, to clear all that down.
(This is probably a bug in test/config.sh)

nonsense · 2021-01-26T12:29:47Z

Could you check if you have a pre-existing address on the weave bridge?

Like ip addr show dev weave.

You may want to do weave reset --force before running the test, to clear all that down.
(This is probably a bug in test/config.sh)

I am getting the same behaviour after doing a weave reset --force - weave:expose still tries to claim the IP that is owned by a container.

This happens at:

cni_connect $HOST1 c0 <<EOF
...
EOF

It is reproducible only with one container and no bridge.

nonsense · 2021-02-01T13:01:24Z

ipam/claim.go

@@ -128,6 +128,9 @@ func (c *claim) Try(alloc *Allocator) bool {
 		// but we also cannot prove otherwise, so we let it reclaim the address:
 		alloc.debugln("Re-Claimed", c.cidr, "for ID", c.ident, "having existing ID as", existingIdent)
 		c.sendResult(nil)
+	case c.ident == "weave:expose":


@bboreham Is weave:expose even a valid identifier for this function? AFAICT this is supposed to be a container ID, so it seems like there is a bug where weave:expose calls this function?

The weave expose command allocates an address for the local machine on the Weave network.
Rather than have a whole different path for that, we pretend we are allocating an address for a container with ID weave:expose.

bboreham · 2021-02-08T19:15:58Z

I suspect the problem is happening here:

weave/plugin/net/cni.go

Line 98 in 34de0b1

bridgeIPResult, err := c.getIP(conf.IPAM.Type, &bridgeArgs)

This part of the CNI plugin wants to set up a gateway address on the bridge so that egress traffic can be routed back into the Weave network. So it calls the IP allocator, with the same CNI config, so it will get an address in the correct subnet. Your new code sees ips field and hands back the IP that you wanted to be allocated for the first container.

I cannot see a simple fix retaining all existing behaviour; that code is deliberately not parsing the config because it wants to be independent of whatever ipam the caller has configured. Maybe we could add another ipam config to be used for gateway address allocation?

I can get your test to otherwise pass by adding weave_on $HOST1 expose before any CNI calls, so the bridge already has an IP when the plugin looks for it.

bboreham · 2021-02-08T19:18:54Z

plugin/ipam/cni.go

+		for j := range ips {
+			ipnet := &net.IPNet{
+				IP:   ips[j],
+				Mask: ips[j].DefaultMask(),


This seems wrong; the IPs are coming back as 10.32.1.42/8 rather than 10.32.1.42/12 which would match the default subnet used by Weave Net.

nonsense mentioned this pull request Jan 16, 2020

sidecar on Kubernetes testground/testground#336

Merged

11 tasks

bboreham reviewed Jan 21, 2020

View reviewed changes

nonsense mentioned this pull request Jan 21, 2020

complete Weave PR for support for ips in ipam config testground/testground#378

Open

raulk mentioned this pull request Mar 11, 2020

decommission our weave fork testground/testground#669

Open

2 tasks

nonsense marked this pull request as draft May 7, 2020 14:05

nonsense force-pushed the support-for-manual-ip branch from b12d4fd to 08afded Compare May 7, 2020 14:08

nonsense commented May 7, 2020

View reviewed changes

nonsense mentioned this pull request May 8, 2020

ipam.IPs string slice testground/testground#977

Draft

bboreham reviewed Jan 18, 2021

View reviewed changes

nonsense marked this pull request as ready for review January 18, 2021 14:58

nonsense force-pushed the support-for-manual-ip branch 3 times, most recently from 9f20d40 to d14fa9e Compare January 25, 2021 15:49

add support for ips in ipam config

49f007f

nonsense force-pushed the support-for-manual-ip branch from d14fa9e to cc28030 Compare January 25, 2021 17:50

nonsense commented Jan 25, 2021

View reviewed changes

basic test to confirm static ip allocation works

32445eb

nonsense force-pushed the support-for-manual-ip branch from cc28030 to 32445eb Compare January 25, 2021 18:01

nonsense commented Feb 1, 2021

View reviewed changes

bboreham reviewed Feb 8, 2021

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

add support for `ips` in ipam config #3754

add support for `ips` in ipam config #3754

nonsense commented Jan 16, 2020 •

edited

Loading

bboreham commented Jan 21, 2020

bboreham left a comment

bboreham Jan 21, 2020

nonsense May 7, 2020

bboreham commented Jan 21, 2020

nonsense commented Jan 22, 2020

bboreham commented Feb 26, 2020

nonsense commented Feb 26, 2020

bboreham commented Feb 26, 2020

nonsense May 7, 2020 •

edited

Loading

bboreham Jan 18, 2021

bboreham left a comment

bboreham Jan 18, 2021

nonsense commented Jan 18, 2021

bboreham commented Jan 18, 2021

nonsense commented Jan 18, 2021

bboreham commented Jan 19, 2021

nonsense commented Jan 19, 2021

nonsense commented Jan 25, 2021 •

edited

Loading

bboreham commented Jan 25, 2021

nonsense Jan 25, 2021 •

edited

Loading

nonsense commented Jan 25, 2021

bboreham commented Jan 25, 2021

bboreham commented Jan 25, 2021

bboreham commented Jan 26, 2021

nonsense commented Jan 26, 2021

nonsense Feb 1, 2021

bboreham Feb 8, 2021

bboreham commented Feb 8, 2021

bboreham Feb 8, 2021

add support for ips in ipam config #3754

Are you sure you want to change the base?

add support for ips in ipam config #3754

Conversation

nonsense commented Jan 16, 2020 • edited Loading

bboreham commented Jan 21, 2020

bboreham left a comment

Choose a reason for hiding this comment

bboreham Jan 21, 2020

Choose a reason for hiding this comment

nonsense May 7, 2020

Choose a reason for hiding this comment

bboreham commented Jan 21, 2020

nonsense commented Jan 22, 2020

bboreham commented Feb 26, 2020

nonsense commented Feb 26, 2020

bboreham commented Feb 26, 2020

nonsense May 7, 2020 • edited Loading

Choose a reason for hiding this comment

bboreham Jan 18, 2021

Choose a reason for hiding this comment

bboreham left a comment

Choose a reason for hiding this comment

bboreham Jan 18, 2021

Choose a reason for hiding this comment

nonsense commented Jan 18, 2021

bboreham commented Jan 18, 2021

nonsense commented Jan 18, 2021

bboreham commented Jan 19, 2021

nonsense commented Jan 19, 2021

nonsense commented Jan 25, 2021 • edited Loading

bboreham commented Jan 25, 2021

nonsense Jan 25, 2021 • edited Loading

Choose a reason for hiding this comment

nonsense commented Jan 25, 2021

bboreham commented Jan 25, 2021

bboreham commented Jan 25, 2021

bboreham commented Jan 26, 2021

nonsense commented Jan 26, 2021

nonsense Feb 1, 2021

Choose a reason for hiding this comment

bboreham Feb 8, 2021

Choose a reason for hiding this comment

bboreham commented Feb 8, 2021

bboreham Feb 8, 2021

Choose a reason for hiding this comment

add support for `ips` in ipam config #3754

add support for `ips` in ipam config #3754

nonsense commented Jan 16, 2020 •

edited

Loading

nonsense May 7, 2020 •

edited

Loading

nonsense commented Jan 25, 2021 •

edited

Loading

nonsense Jan 25, 2021 •

edited

Loading