-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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.
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
Fedora coreos networkmanager global dns and bootstrapping fix #6577
Conversation
Hi @spaced. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
03295d1
to
6fb0170
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miouge1, spaced The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
…etes-sigs#6577) * remove podman cni plugin * configure networkamanger global dns * allow installation of python3-libselinux by disabling update repo temporary * remove ipv4 section because it is not a valid configuration
What type of PR is this?
/kind bug
What this PR does / why we need it:
NetworkManager
dns configurationAllows to have other connections than
default_connection.nmconnection
(for example abond
configuration)-- removing podman network cni plugin
-- disabling fedora-updates.repo before installing
python3-libselinux
packageWhich issue(s) this PR fixes:
Fixes #591
Special notes for your reviewer:
I can split the commits in two different
PRs
if required, because it solves different issues.Does this PR introduce a user-facing change?: