Fix kubelet for Fedora CoreOS 36 to provide real resolvconf to contai… #97
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ners.
In Fedora CoreOS 36 CoreDNS cannot start correctly due to a loopback issue where /etc/resolv.conf is mounted and points to localhost.
Tested on Fedora CoreOS 35,36,37, with Docker and containerd.
https://coredns.io/plugins/loop/#troubleshooting-loops-in-kubernetes-clusters https://fedoraproject.org/wiki/Changes/systemd-resolved#Detailed_Description
Story: 2010519
Change-Id: I8106324ce71d6c22fa99e1a84b5a09743315811a (cherry picked from commit 111645ecc625cff1cedab21f53841b2ac2200fff)