Skip to content
This repository has been archived by the owner on Jul 30, 2024. It is now read-only.

deploy static IPs to CoreOS nodes #9

Closed
rmkraus opened this issue May 6, 2020 · 4 comments
Closed

deploy static IPs to CoreOS nodes #9

rmkraus opened this issue May 6, 2020 · 4 comments
Labels
enhancement New feature or request

Comments

@rmkraus
Copy link
Member

rmkraus commented May 6, 2020

Either optionally or by default, CoreOS nodes should get static IPs after they are provisioned.

Reference:
https://www.openshift.com/blog/openshift-4-bare-metal-install-quickstart

@rmkraus rmkraus added the enhancement New feature or request label May 6, 2020
@rmkraus
Copy link
Member Author

rmkraus commented May 6, 2020

Maybe this should also support bonded interfaces?

@rmkraus rmkraus closed this as completed Jul 2, 2021
@rmkraus rmkraus reopened this Jul 2, 2021
rmkraus added a commit that referenced this issue Jul 3, 2021
A new configuration option has been added to specify the NIC on the node
to use for cluster traffic. If this is not specified, the node will dhcp
boot all interfaces. If this is specified, the node will now configure
that interface with a static ip to eliminate the need to DHCP post
install.

This addresses #9
rmkraus added a commit that referenced this issue Jul 9, 2021
A new configuration option has been added to specify the NIC on the node
to use for cluster traffic. If this is not specified, the node will dhcp
boot all interfaces. If this is specified, the node will now configure
that interface with a static ip to eliminate the need to DHCP post
install.

This addresses #9
rmkraus added a commit that referenced this issue Jul 11, 2021
* Added support for static IP addresses on cluster nodes.

A new configuration option has been added to specify the NIC on the node
to use for cluster traffic. If this is not specified, the node will dhcp
boot all interfaces. If this is specified, the node will now configure
that interface with a static ip to eliminate the need to DHCP post
install.

This addresses #9

* Added support for bonding interfaces.

This addresses #129. It is up to the user to ensure the infrastructure
is setup to handle the bond that is configured. That is out of scope of
the installer.
@rmkraus
Copy link
Member Author

rmkraus commented Jul 12, 2021

released in 4.7.2

@rmkraus rmkraus closed this as completed Jul 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant