Skip to content

Openstack provider: Revisit instance name source #62295

@alvaroaleman

Description

@alvaroaleman

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.name again, which will remove a lot of friction of the OS provider and keep feature parity to status quo
  • Use metadata.uuid which 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

No one assigned

    Labels

    area/provider/openstackIssues or PRs related to openstack providerlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions