Skip to content

Add alternative to PrivateDnsName on AWS cloud provider #52241

@greenboxal

Description

@greenboxal

/kind feature

AWS cloud provider forces the hostname, or at least the node name, to be the same as AWS' PrivateDnsName, this leads to the node being removed if a different node name is used.

It should be allowed to use any name as the node name and map it to a tag.

Is there any problem with this? I can provide a PR. It's really cumbersome to use ip-x-x-x-x.region.compute.internal as it doesn't pair with the rest of my infrastructure.

Environment:

  • Kubernetes version (use kubectl version): 1.7.5
  • Cloud provider or hardware configuration: AWS
  • OS: Arch Linux
  • Kernel (e.g. uname -a): Linux ip-10-0-50-10 4.12.8-1-ec2 Unit test coverage in Kubelet is lousy. (~30%) #1 SMP Mon Aug 21 22:43:04 PDT 2017 x86_64 GNU/Linux
  • Install tools: None

Metadata

Metadata

Assignees

Labels

area/provider/awsIssues or PRs related to aws providerkind/featureCategorizes issue or PR as related to a new feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.sig/cloud-providerCategorizes an issue or PR as relevant to SIG Cloud Provider.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions