Enable customization of Docker networks about vcenter-event-broker-appliance

[rhjensen79]

New version is working for me. None of the old versions were working, and I'm on a 172.17.x.x network.
So I think I found out why. Thanks for the update.

[lamw]

Thanks for the feedback Mark. This has been the first request we've had regarding the default bridged network for Docker. We did run into a similar issue w/Pod CIDR that could conflict with an existing network. I think it makes sense to support customizing this just like we do with Pod CIDR as an "Advanced Option".

Leaving https://success.docker.com/article/how-do-i-configure-the-default-bridge-docker0-network-for-docker-engine-to-a-different-subnet as a note

[virtualhobbit]

Thanks, William.

Let me know if you'd like me to guinea pig anything :-)

[lamw]

Here's Beta build of VEBA https://download3.vmware.com/software/vmw-tools/veba/vCenter_Event_Broker_Appliance_0.4.0-beta.ova which introduces Advanced Setting for customizing the Docker Bridge Network. By default it will use 172.26.0.1/16 which is a default from Docker.

Here's example deploying VEBA overriding the default Docker Bridge Network using value of 172.30.0.1/16

Give this a try @virtualhobbit and let me know if it resolves the issue and unblocks you from giving VEBA a try in your env :)

[lamw]

@virtualhobbit Per Twitter discussion, it looks like the code prevented 172.26.0.1/16 as I mixed up the default Docker Bridge network with your desired address. This has been fixed and I've also verified in my own env. You can grab the updated OVA at https://download3.vmware.com/software/vmw-tools/veba/vCenter_Event_Broker_Appliance_0.4.0-beta.ova

[virtualhobbit]

Yup, can confirm this is now sorted with that build! Thanks @lamw!