Skip to content

fix: added new warning about subnet size #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
n3rdc4ptn merged 2 commits into from
Feb 11, 2026
Merged

fix: added new warning about subnet size #35

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6591dfe
fix: added new warning about subnet size
n3rdc4ptn Feb 11, 2026
6c9b37c
Update docs/operators/01-boostrapping.md
n3rdc4ptn Feb 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 22 additions & 3 deletions docs/operators/01-boostrapping.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ docker pull ghcr.io/openmcp-project/images/openmcp-bootstrapper:${OPENMCP_BOOTST

### Requirements

* [Docker](https://docs.docker.com/get-docker/) installed and running. Docker alternatively can be replaced with another OCI runtime (e.g. Podman) that can run the `openmcp-bootstrapper` CLI tool as an OCI image.
* [Docker](https://docs.docker.com/get-docker/) installed and running. Docker alternatively can be replaced with another OCI runtime (e.g. Podman) that can run the `openmcp-bootstrapper` CLI tool as an OCI image.
* [Kind](https://kind.sigs.k8s.io/docs/user/quick-start/) installed

:::info
Expand Down Expand Up @@ -125,8 +125,27 @@ nodes:

Create the Kind cluster using the configuration file created in the previous step.

:::info
:::warning

Please check if your current `kind` network has a `/16` subnet. This is required for our cluster-provider-kind.
You can check the current network configuration using:

```shell
docker network inspect kind | jq ".[].IPAM.Config.[].Subnet"
"172.19.0.0/16"
```

If the result is not specifying `/16` but something smaller like `/24` you need to delete the network and create a new one. For that **all kind clusters needs to be deleted**. Then run:

```shell
docker network rm kind

docker network create kind --subnet 172.19.0.0/16
```

:::

:::info Podman Support
In case you are using Podman instead of Docker, it is currently required to first create a suitable network for the Kind cluster by executing the following command before creating the Kind cluster itself.

```shell
Expand Down Expand Up @@ -467,7 +486,7 @@ You are now ready to create and manage clusters using openMCP.
### Get Access to the Onboarding Cluster

The openmcp-operator should now have created a `onboarding Cluster` resource on the platform cluster that represents the onboarding cluster.
The onboarding cluster is a special cluster that is used to create new managed control planes.
The onboarding cluster is a special cluster that is used to create new managed control planes.

```shell
kubectl --kubeconfig ./kubeconfigs/platform.kubeconfig get clusters.clusters.openmcp.cloud -A
Expand Down