-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws: Retrieve instance info only when max pods is not set #16216
Conversation
/retest |
36271a0
to
b425002
Compare
/retest |
/hold |
b425002
to
91b261c
Compare
}) | ||
if err != nil { | ||
return nil, fmt.Errorf("error describing instances: %v", err) | ||
if localHostname, err := metadata.GetMetadata("local-hostname"); err == nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We used to have an issue (IIRC) where local-hostname did not match PrivateDNSName, when users had a VPC with a custom DNS suffix. However, I think that we're now OK because (1) we use the instance ID as the node name now, rather than PrivateDNSName and (2) kubeletNames seems to mostly be ignored now anyway, as we usually issue the cert via kops-controller.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb, rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold |
/cc @zetaab @rifelpet
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kops/16204/presubmit-kops-aws-scale-amazonvpc-using-cl2/1742822642840244224/artifacts/i-0005fc01059a34f29/kops-configuration.log