DNS Names as endpoints about etcd-aws-cluster

[tjcorr]

I'm not sure I understand what you are asking for. Are you suggesting that instead of using the IP address for the peer URLs we would replace them with the AWS DNS entries (like ec2-34-197-7-63.compute-1.amazonaws.com vs 34.197.7.63)? If so I'm not what would be the benefit.

[kenden]

If we have etcd in an autoscaling group, it could be nice to have an ELB sending request from etcd clients to the etcd ec2 instances members of this autoscaling group.

And if we have an ELB, it's would be nice we have a better DNS/Route53 endpoint pointing to it.

[prashantchitta]

@tj-corrigan I am using DNS names like https://ip-10-0-0-181.us-west-2.compute.internal:2379. As a result its failing the regex validation and unable to find the bad peer even though bad peer exists. This is the error it throws

peer_regexp=https://ip-10-0-0-126.us-west-2.compute.internal:2379 or https://ip-10-0-0-129.us-west-2.compute.internal:2379 or https://ip-10-0-0-181.us-west-2.compute.internal:2379

jq: error: syntax error, unexpected ':', expecting ';' or ')' (Unix shell quoting issues?) at <top-level>, line 1:
.[] | map(select(.peerURLs[] | https://ip-10-0-0-126.us-west-2.compute.internal:2379 or https://ip-10-0-0-129.us-west-2.compute.internal:2379 or https://ip-10-0-0-181.us-west-2.compute.internal:2379 | not )) | .[].id
jq: 1 compile error
bad_peer=

bad_peer is empty as a result of above error.
Is it possible to change the regex to accommodate DNS entries like above?

[prashantchitta]

I fixed it for domain names. regex has to be changed to the following
[-a-z0-9.]*\)