- Notifications
You must be signed in to change notification settings - Fork 42k
Closed
Labels
area/provider/openstackIssues or PRs related to openstack providerIssues or PRs related to openstack providerlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Description
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
In an attempt to make the Openstack cloud provider work with instance names that are not dns-conformant it was changed to use metadata.hostname instead of metadata.name as in pre-1.10.
This did not solve the original issue (working with non-dns-conformant instances) but created another set of issues. The course that led to this is best described in this comment by @voelzmo.
We should now decide if we want to
- Go back to use
metadata.nameagain, which will remove a lot of friction of the OS provider and keep feature parity to status quo - Use
metadata.uuidwhich will make the OS provider work with non-dns-compliant instance names but result in weird node names
CC @dims @hogepodge
/sig-openstack
Metadata
Metadata
Assignees
Labels
area/provider/openstackIssues or PRs related to openstack providerIssues or PRs related to openstack providerlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.