Skip to content

Add note on avoiding conflicting subnets for EDA VM #32

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

Draft
pratdesai91 wants to merge 1 commit into
base: release-25.12
Choose a base branch
from
Draft

Add note on avoiding conflicting subnets for EDA VM #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions docs/software-install/deploying-eda/setting-up-the-eda-virtual-machine-nodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -279,6 +279,8 @@ Kubernetes pods and services network settings.
- 10.96.0.0/12
- fd31:e17c:f07f:2dc0:4e2b:2ebc:cbc0:0/108
```
**Note:- Avoid using 172.16-19.X.X subnets as they conflict with hypervisor Docker subnets causing cluster bootstrappign issues.**
Copy link
Copy Markdown
Contributor

@hellt hellt Mar 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @pratdesai91
where did you observe the issues? Did you try to install this on a Talos or something else?

I am asking because there is no Docker on Talos setups

Copy link
Copy Markdown
Author

@pratdesai91 pratdesai91 Mar 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @hellt

These use cases are only applicable when the hypervisor itself also hosts the edaadm package server.

In most customer environments, there is no separate jump‑box provided for running the image‑processing or configuration‑rendering steps. Because of that limitation, I typically install Docker directly on Hypervisor‑1 to run the kpt‑setter workflow required for an air‑gapped EDA installation.

This ensures that all rendering, packaging, and artifact preparation can be completed locally on the hypervisor, even when external registry access or an intermediate workstation is not available.



* `node-cidr-mask-size-ipv4`: Defines the subnet mask size for IPv4 network as defined by the `podSubnets` that each node will use.
Default: `24`
Expand Down