Skip to content

Explain why MCO+Ignition may not work for bond/vlan #2

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
SchSeba merged 1 commit into from
May 4, 2020
Merged

Explain why MCO+Ignition may not work for bond/vlan #2

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
4 changes: 4 additions & 0 deletions enhancements/kubernetes-nmstate-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,6 +103,10 @@ An upstream API group of nmstate.io is currently used.
#### Bond creation

* Be able to create bond interfaces on OpenShift nodes.

Typically, MCO + Ignition would be utilized. However, in a Day 1 install, that may not be possible.
It may be necessary for the bond/vlan configuration be done before Ignition can even be reached.

* Create a vlan interface on top of the bond inter.

#### Assign ip address
Expand Down