A Tool to add multiple IPs to NICs in Azure VMs

To build the binary, simply run make.

To wrap up the binary in a docker alpine container, run make image

To run the container, launch it with:

$ docker run -e APP_ID={AZURE_SP_ID} -e APP_SECRET={AZURE_SP_SECRET} -e ACCOUNT_ID={AZURE_SUBSCRIPTION_ID} -e TENANT_ID={AZURE_TENANT_ID} -e GROUP_NAME={RESOURCE_GROUP_NAME_WITH_VM} -e VM_NAME={NAME_OF_VM_IN_RG} docker4x/az-nic-ips:latest

You should see a new IP added to the first NIC of VM with VM_NAME

1. Create a azure_ucp_admin.json file with the following information:

aadClientId = "<AD App ID >"
tenantId = "<AD Tenant ID >"
subscriptionId = "<Azure subscription ID>"
aadClientSecret = "<AD App Secret >"

2. Create a Docker Swarm secret based on the "azure_ucp_admin.toml" file

docker secret create azure_ucp_admin.json azure_ucp_admin.json

3. Create a global swarm service using this image

docker service create \
  --mode=global \
  --secret=azure_ucp_admin.json \
  --log-driver json-file \
  --log-opt max-size=1m \
  --env IP_COUNT=128 \
  --name ipallocator \
  docker4x/az-nic-ips:latest

By default (as deployed with Docker EE 3.1.0 >) the service will read the cloud attribute (e.g. AzureChinaCloud, AzureGovCloud) from /etc/kubernetes/azure.json and determine the correct Resource Manager Endpoint. If the attribute is not present, the default of AzurePublicCloud will be used. It is possible to manually override that behavior in either case by passing the RESOURCE_MANAGER_ENDPOINT environment variable to the container / service.

Note: RESOURCE_MANAGER_ENDPOINT must be set directly to the URL of the endpoint, not the name of the Cloud. To find the correct URL for the desired region consult the Microsoft Azure documentation.

It is possible to skip allocating IP addresses to a particular VM by applying a tag with the name k8skipIP to the VM (the value does not matter).

It is possible to select the NIC that that IP addresses are allocated to. This is achieved by applying a tag with the name PodNIC to the Network Interface (the value does not matter). If there is a single NIC with that tag, it will be used. If no NIC with that tag exists, the service will instead look for the Primary NIC and allocate to that.

Note: Specifying multiple NICs for a single VM with the tag PodNIC is not allowed and will error. The service will also error if no suitable NICs can be found.