Maksytka/kind
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/kind.git synced 2025-12-01 07:26:05 +07:00
Code Issues Packages Projects Releases Wiki Activity

make IP conflict doc more general

Browse Source
This commit is contained in:
mwdomino
2025-05-05 16:04:04 -04:00
parent dd85f47bf2
commit be370e4684
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
site/content/docs/user/known-issues.md
View File

@@ -41,7 +41,7 @@ description: |-
* [Docker Desktop for macOS and Windows](#docker-desktop-for-macos-and-windows) * [Docker Desktop for macOS and Windows](#docker-desktop-for-macos-and-windows)
* [Older Linux Distributions](#older-linux-distributions) * [Older Linux Distributions](#older-linux-distributions)
* [Failure to Create Cluster on WSL2](#failure-to-create-cluster-on-wsl2) * [Failure to Create Cluster on WSL2](#failure-to-create-cluster-on-wsl2)
* [VPN CIDR clashes](#vpn-cidr-clashes) * [Local Subnet Clashes](#local-subnet-clashes)
## Troubleshooting Kind ## Troubleshooting Kind
@@ -417,11 +417,11 @@ the project relies on community support and feedback. It has been noted that the
steps detailed in [https://github.com/spurin/wsl-cgroupsv2](https://github.com/spurin/wsl-cgroupsv2) steps detailed in [https://github.com/spurin/wsl-cgroupsv2](https://github.com/spurin/wsl-cgroupsv2)
have been necessary to resolve this issue. have been necessary to resolve this issue.
## VPN CIDR Clashes ## Local Subnet Clashes
KIND creates a separate docker network named `kind` that will be configured with default IPAM settings. If you are using the default IPAM configuration in your `daemon.json` you KIND creates a separate docker network named `kind` that will be configured with default IPAM settings. If you are using the default IPAM configuration in your `daemon.json` you
may have conflicts with existing VPNs that route the 172.17.x.x networks. To resolve this you can reconfigure the daemon-wide IPAM so that all networks will be created in subnets may have conflicts with existing networks (like VPNs, labs, etc) that route the 172.17.x.x networks. To resolve this you can reconfigure the daemon-wide IPAM so that all
that do not have these conflicts. networks will be created in subnets that do not have these conflicts.
An example configuration that you can add to your `daemon.json` is below. This would configure `10.253.0.0/16` as the defauld CIDR with each individual network receiving a /24 An example configuration that you can add to your `daemon.json` is below. This would configure `10.253.0.0/16` as the defauld CIDR with each individual network receiving a /24
subnet to use for allocation. subnet to use for allocation.