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. https://github.com/openshift/ose/pull/624
Pull request went through.
This has been merged into ocp and is in OCP v3.5.0.33 or newer.
Verified on both RPM and image. Fixed. # openshift version openshift v3.5.0.33 kubernetes v1.5.2+43a9be4 etcd 3.1.0
This never made it to the customers, thus doesn't need to be in an errata. Closing.