I'm not sure why this isn't still fixed for 3.5, but it isn't.
The process that origin, and thus OCP/atomic-openshift, sets these variables is being re-worked. It will be another week before any progress is seen on this bug.
Hi Troy, Any update on this? Have the changes landed upstream?
The changes did land upstream, causing different changes. But now I can work with them and get them fixed.
Fixed with this pull request.
Pull request went through.
This has been merged into ocp and is in OCP v220.127.116.11 or newer.
Verified on both RPM and image.
# openshift version
This never made it to the customers, thus doesn't need to be in an errata. Closing.