Calico IP range should be a config option

[Tim Van Steenburgh]

Opened by Cynerva on 2017-02-02 18:31:13+00:00 at https://github.com/juju-solutions/layer-calico/issues/4

------------------------------------------------------------

We're using a hardcoded 192.168.0.0/16 range right now. It needs to be a config option.
From #1:

Config would be better extended to specify the IP range (default is 192.168.0.0/16). To change this, configure_calico_pool() should delete the existing pool and create a new one with the IPIP/nat-outgoing options.

[Dmitrii Shcherbakov (dmitriis)]

It should be a bit more elaborate as there can be many pools per a single Calico deployment:

https://docs.projectcalico.org/v3.5/reference/calicoctl/resources/ippool

I would suggest making the configuration of an out-of-the-box pool optional and making pool management doable via actions as this is something user-defined. Calico charm could warn a user that there are no pools configured via charm status.

[Tim Van Steenburgh (tvansteenburgh)]

Dmitrii what's the urgency on this?

[George Kraft (cynerva)]

Fixed by https://github.com/charmed-kubernetes/layer-calico/pull/33, which is available with cs:~containers/calico-630 in the edge channel.

The fix makes the CIDR configurable:

juju config calico cidr=192.168.0.0/16

And makes it possible to bypass charm pool management so you can manually configure multiple pools if needed:

juju config calico manage-pools=false
juju ssh calico/0 calicoctl apply -f - << EOF
apiVersion: projectcalico.org/v3
kind: IPPool
metadata:
  name: my-pool
spec:
  cidr: 192.168.0.0/24
  ipipMode: Never
  natOutgoing: true
EOF