Enable override for Cluster CIDR and Pod CIDR when creating management cluster or target cluster

[PragyaDw]

Several customers have workloads in the cloud in AKS or other clouds and extend their on-premises networks into the cloud. This can lead to address conflicts in the rather large ranges of 10.96.0.0/12 and 10.244.0.0/16.

Customers are asking us to allow them to change these values to smaller ranges matching their target cluster needs.
High Level goals:
Add podCIDR and serviceCIDR to the New-AksHciNetworkSettings and New-AksHciClusterNetwork commands
Apply these settings during the kubadm join phase in cloud-init and cloudbase-init for Linux and Windows respectively
Non Goals:
Allow to change the CIDR after deployment of a cluster

[chris8205]

Vote UP...

It is an important core function/configuration that is needed. The network cannot be restructured.
As a temporary measure, 100.60.0.0/10 /16 can be specified in the source deployment instead of 10.244.0.0/16
This network is usually only used by ISPs for routing purposes