Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1845199

Summary: backport upstream patch 91500 into openshift
Product: OpenShift Container Platform Reporter: Ryan Phillips <rphillips>
Component: NodeAssignee: Ryan Phillips <rphillips>
Status: CLOSED DUPLICATE QA Contact: Sunil Choudhary <schoudha>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.6CC: aos-bugs, jokerman
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-08 21:05:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ryan Phillips 2020-06-08 15:58:22 UTC 
Description of problem:
If the pod originates from the kube-api, when we know that the kube-apiserver is responding and the kubelet's credentials are valid. Knowing this, it is reasonable to wait until the service lister has synchronized at least once before attempting to build a service env var map. This doesn't present the race below from happening entirely, but it does prevent the "obvious" failure case of services simply not having completed a list operation that can reasonably be expected to succeed. One common case this prevents is a kubelet restart reading pods before services and some pod not having the KUBERNETES_SERVICE_HOST injected because we didn't wait a short time for services to sync before proceeding. The KUBERNETES_SERVICE_HOST link is special because it is unconditionally injected into pods and is read by the in-cluster-config for pod clients

PR https://github.com/kubernetes/kubernetes/pull/91500

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Ryan Phillips 2020-06-08 21:05:54 UTC 

*** This bug has been marked as a duplicate of bug 1839098 ***