Open dwmkerr opened 6 years ago
Just a note to let you know this issue still isn't fixed with Openshift 3.9 unfortunately.
Thanks for the heads up @bjwschaap, I'll keep the issue open and cross my fingers for 3.10!
This may never be fixed - https://github.com/openshift/openshift-ansible/issues/9665 suggests that openshift_hostname
has been removed, as private 'vanity names' seemed to cause issues. Investigate later
Does this mean we can't run this deployment on a private subnet using private ip/dns names?
Note
This may be fixed with the latest version (3.9 at the time of writing) but needs to be tested.
Details
When we use the AWS Cloud Provider (which is required for Persistent Volumes (see #33)), we lose the ability to name our nodes, e.g:
Becomes:
This does not cause any functional problems, but is frustrating for users as it makes it hard to identify nodes.
The root cause seems to be:
The following issue is also related: