Bug 1891781 - dnsPolicy of kube-scheduler apiserver and controller-manager not aligned with hostNetwork
Summary: dnsPolicy of kube-scheduler apiserver and controller-manager not aligned with...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.5.z
Assignee: Maciej Szulik
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On: 1891779
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-27 10:58 UTC by Maciej Szulik
Modified: 2020-11-03 16:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1891779
Environment:
Last Closed: 2020-11-03 16:30:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Maciej Szulik 2020-11-03 16:30:55 UTC 
This change is causing issues during startup b/c ClusterFirstWithHostNet dns policy forces in-cluster dns server which is not available during core elements startup.
I'm currently discussing how to solve this issue for kubelet first. I'm closing this as won't fix for now.
Note You need to log in before you can comment on or make changes to this bug.