Thanks to visit codestin.com
Credit goes to github.com

Skip to content

kubectl can not resolve EC2 instance IDs (AWS) #10612

@antoineco

Description

@antoineco

Regression introduced in #9728

Some kubectl subcommands like logs rely on the node name to perform an API call, and fail if this name is not resolvable:

Example:

$ kubectl logs api-9iqef
Error from server: Get https://i-0f4ab5f6:10250/containerLogs/default/api-9iqef/api: dial tcp: lookup i-0f4ab5f6: no such host

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions