Long term we hope to be able to get the metadata needed from the kubelet. It already has some/all of the metadata needed, it is just a question of providing an authenticated endpoint on the kubelet API. This is definitely post-3.4.
*** Bug 1386693 has been marked as a duplicate of this bug. ***
Is there something we can do to mitigate this problem with OCP 3.4? Should we target this bug for OCP 3.5?
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers. Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant. This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.