Users with some specific network environments have discovered unexpected network behavior when trying to create a DKP 2.X bootstrap cluster.
Symptoms might include log messages about being unable to pull images from remote image registries or otherwise being unable to resolve certain domain names.
This behavior is usually related to your /etc/resolv.conf file being mounted from the host machine into the bootstrap cluster containers in KinD.
Values that are necessary on the host machine, such as search paths, might interfere with the operation of the containerized bootstrap cluster.
The workaround for this issue is to temporarily edit your host machine's /etc/resolv.conf file to only contain your environment's upstream DNS resolvers before creating a bootstrap cluster, then revert your changes once the bootstrap cluster is no longer required.
More details can be found in this article about a related issue with a similar workaround: