Expose Availability Zone ID in addition to name about envars-from-node-labels HOT 3 CLOSED

@sergey-kalin, I was looking at a proper way to solve this, because like I said earlier it doesn't feel the right solution making calls into AWS control plane from a webhook.

There is a way to add additional node labels from the worker bootstrap script (i.e. /etc/eks/bootstrap.sh). The way you go about this is to use kubelet-extra-args with the bootstrap script.

So you're going to have a little script that would make a curl request into AWS metadata plane to find the zone ID mapping, then create new labels with kubelet-extra-args in the same script. You wrap it all together by running the script from a terraform launch template at EKS cluster creation time:

{
  filename     = "custom-labels.sh"
  content_type = "text/cloud-boothook"
  vars         =  {}
}

from envars-from-node-labels.

@danfromtitan I'm using Java version of aws ec2 describe-availability-zones actually, just getting all zones visible to container and filtering one needed.

There is same method for Go SDK - https://docs.aws.amazon.com/sdk-for-go/api/service/ec2/#EC2.DescribeAvailabilityZones

Please mind it requires ec2:DescribeAvailabilityZones permission granted through e.g. service account

from envars-from-node-labels.

This is a use case on the very edge of the implementation design, mainly because zone IDs are specific to a subscription account, not so much to an EKS node. I understand the usefulness of it though, so I'll add a zone ID label next to the zone name.

What is the API call you're making now to determine the zone ID @sergey-kalin ?

from envars-from-node-labels.