Docker Network - allow customizable subnet or remove static route

The default subnet of `172.17.0.0/16` is somewhat problematic in enterprise environments that use that subnet schema for servers or workstations.

For example, we have a user who’s laptop is assigned an IP in that range (ex – `172.17.132.69/24`). They will have routing issues hitting anything on our Kubernetes cluster because the default Docker network is `172.17.0.0/16` and there’s a static route on all the worker nodes:


Since AKS-on-HCI is not using Docker network, can we remove this during install? If not, can we have a way in the AKS installation cmdlet to override this subnet?

Start with the AKS installation cmdlet and trace how the default Docker network and its static route are configured. Determine whether installation can remove the route or accept a customizable subnet, then verify that the selected behavior avoids conflicts with enterprise networks.

Written by the indexing model from the issue text.