Add VPC IP and Elastic IP to ECS node as private and public IP #1954
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As per documentation [1], the InnerIpAddress field is only relevant
when the node network type is set to classic. If the node is within
a VPC, the private IP is returned by the VpcAttributes/PrivateIpAddress.
In addition, elastic IPs in field EipAddress are also public ips.
They differ from other public IPs in that they are static and stay
the same once allocated.
Fields EipAddress and VpcAttributes are already returned in the response
as part of the "extra" field of the node object. This is however not
consistent with other drivers as these fields are also public and
private IP addresses, respectively.
[1] https://www.alibabacloud.com/help/en/ecs/developer-reference/api-describeinstances
Status
Checklist (tick everything that applies)