-
Notifications
You must be signed in to change notification settings - Fork 38.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 for cloud-controller-manager #47215
Conversation
Hi @ublubu. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
return "", fmt.Errorf("ProviderID \"%s\" didn't match expected format \"aws://InstanceID\"", providerID) | ||
} | ||
|
||
return matches[1], 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.
This will cause OutOfIndex error.
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.
Oh whoops. Fixed it and added a test for this.
@ublubu how was the kubelet obtaining node addresses before? Was it using the metadata service? I'm asking because I'm wondering why there is a new function to describe addresses. Shouldn't there be existing methods for this very purpose? |
@wlan0 The kubelet uses the local metadata service. In the kubelet: kubernetes/pkg/kubelet/kubelet_node_status.go Line 432 in b8c9ee8
AWS implementation of NodeAddresses using metadata service:
IIUC, the new methods are run in the CCM on a master, where a node's metadata service is not available. |
@k8s-bot ok to test |
/lgtm @dchen1107 same question - 1.7.0 or 1.7.1? |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: thockin, ublubu Associated issue: 47214 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@k8s-bot pull-kubernetes-e2e-gce-etcd3 test this |
Addresses #47257 |
@k8s-bot pull-kubernetes-e2e-gce-etcd3 test this |
@thockin May I set the v1.7 label on this? |
@dchen1107 this is thoroughly flag gated already |
Automatic merge from submit-queue |
It seems this PR uses an incompatible provider id format. |
What should the format be? |
Addressed in #47395 I believe |
@justinsb Thanks! |
fixes #47214
This implements the NodeAddressesByProviderID and InstanceTypeByProviderID methods used by the cloud-controller-manager for the AWS provider.
NodeAddressesByProvider uses DescribeInstances (for normal addresses) and DescribeAddresses (for Elastic IP addresses).
InstanceTypeByProviderID uses DescribeInstances.