kubermatic / kubermatic/docs

Document static IP requirements for Nodes/Machines

Open
#1,444 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

lifecycle/frozen
Dominant language
SCSS
Stars
19
Forks
117
Avg merge
13h 29m
Merged PRs (30d)
13

Description

We discussed and agreed on SIG Cluster Management that the ecosystem is pretty clearly expecting static IPs on Nodes, or to be more precise: Systems not changing their primary IP address once a cluster has been joined.

For now, we would like to document the requirement that VMs / hardware nodes get the same IP address assigned, even after reboots or DHCP leases expiring.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Nodes/Machines documentation and the section describing node networking or cluster requirements. Document that VM and hardware nodes must retain the same primary IP address after reboots and DHCP lease expiration; done means the requirement is clear in the relevant documentation.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.