Skip to content
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

Jump to bottom

Document static IP requirements for Nodes/Machines #1444

Open
embik opened this issue May 9, 2023 · 6 comments
Open

Document static IP requirements for Nodes/Machines #1444

embik opened this issue May 9, 2023 · 6 comments
Assignees
@embik
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@embik
Copy link
Member

embik commented May 9, 2023

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.
@embik embik self-assigned this May 9, 2023
@embik embik mentioned this issue Jun 2, 2023
Open
@embik
Copy link
Member Author

embik commented Jun 2, 2023

Also see kubermatic/kubermatic#12218 for the investigation and code in the KubeVirt CCM that does not allow node changes.

@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 31, 2023
@embik
Copy link
Member Author

embik commented Sep 1, 2023

/remove-lifecycle stale

@kubermatic-bot kubermatic-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 1, 2023
@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 30, 2023
@kubermatic-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@kubermatic-bot kubermatic-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 30, 2023
@embik
Copy link
Member Author

embik commented Jan 2, 2024

/remove-lifecycle rotten

@kubermatic-bot kubermatic-bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale. label Jan 2, 2024
@embik embik added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@embik embik

Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@embik @kubermatic-bot