This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
Remove .spec.network.mode, make it instance-specific
#310
Assignees
Labels
api/v1alpha2
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
Comments
luxas
added
api/v1alpha2
kind/api-change
This was referenced Aug 12, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Instead of letting the user specify in the desired VM state what networking plugin or container runtime to use, this should be an option for the
ignite(d)instance that receives the desired state and makes it happen. This way VM specifications are portable, and do not need to be tweaked for different environments.Instead of
.spec.network.mode, we'll use a--net-plugingloabl flag (maybe env var/config file in the future, too)The text was updated successfully, but these errors were encountered: