How to update Docker bridge CIDR for AKS to a different subnet

@Raj Dn Apologies for delay in response and all the inconvenience caused because of the issue.

We don’t use the docker bridge for pod communication, but as Docker is configured as part of the Kubernetes setup, this docker bridge it also gets created as well, so in order to avoid that it picks random unknown CIDR that could collide with any of your existent subnets, we give the option to change it and set it a known range. So the indication for docker bridge is to define any CIDR that doesn’t to Azure, and doesn’t collide with any other subnet. The Docker bridge network address represents the default docker0 bridge network address present in all Docker installations. While docker0 bridge is not used by AKS clusters or the pods themselves, you must set this address to continue to support scenarios such as docker build within the AKS cluster. It is required to select a CIDR for the Docker bridge network address because otherwise Docker will pick a subnet automatically which could conflict with other CIDRs. You must pick an address space that does not collide with the rest of the CIDRs on your networks, including the cluster's service CIDR and pod CIDR. You can reuse this range across different AKS clusters.

Any service of the clusterIP the type that you create from Kubernetes will get an IP from this CIDR, but this IP is only available in the cluster.

Since this is created at time of setup you cannot change or update the Docker Bridge CIDR.

More information here.

Also this range should not be used by any network element on or connected to this virtual network. Service address CIDR must be smaller than /12. You can reuse this range across different AKS clusters.

Hope it helps!!!

Please "Accept as Answer" so it can help others in community looking for help on similar topics.