Allow flannel CNI to work with kicbase by fixing IP conflict #9046
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows
minikube start --driver=docker --cni=flannel
to work. It previously starts, but DNS would fail to come up due to:Warning FailedCreatePodSandBox 56m kubelet, minikube Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "efd353915df8d27b733e20492a3ad43294cb42dc1e17119981c13ba21a233ded" network for pod "coredns-f9fd979d6-jxvx5": networkPlugin cni failed to set up pod "coredns-f9fd979d6-jxvx5_kube-system" network: failed to set bridge addr: "cni0" already has an IP address different from 10.244.0.1/24
This was noticed while testing different CNI environments on Docker.