英文:
Why are my EKS cluster nodes having different name scheme?
问题
我正在学习如何使用EKS，并且我有3个集群，一个在ap-south-1，另外两个在us-east-1。这3个集群都已经配置成相同的方式，至少我已经尝试过，每个集群都有3个节点。但是ap-south-1集群中的节点名称看起来与us-east-1中的2个集群中的节点名称不同。
ap-south-1集群中的节点形式为 ip-<IP>.ap-south-1.compute.internal。
而us-east-1中的2个集群中的节点形式为 ip-<IP>.ec2.internal。
现在，我没有足够的信息来确定这是否是一个地区性的问题，但我尝试在这些集群中创建新的节点组，它们都遵循各自的命名方案。
不要误解我，一切都没有问题，但这种行为让我感到困惑，我找不到任何信息。希望能提供一些见解！
英文:
I am learning to work with EKS and I have 3 clusters, 1 in ap-south-1 and 2 in us-east-1. All 3 clusters have been configured the same way, at least I have tried to and each have 3 nodes. But the node names in the ap-south-1 cluster looks different from the node names in the 2 clusters in us-east-1.
The nodes in the ap-south-1 cluster is of the form ip-<IP>.ap-south-1.compute.internal.
The nodes in the 2 east-us-1 clusters is of the form ip-<IP>.ec2.internal.
Now, I don't have enough information to know if this is a regional thing or not, but I tried to create new nodegroups in the clusters and they are following their respective naming schemes.
Don't misunderstand me, there is nothing wrong at all but this behaviour has thrown me off and I can't find any info anywhere. Some insight would be great!
答案1
得分: 1
这似乎只是不同地区实施之间的一个不重要的不一致性。文档未说明原因，所以这句话只是一个猜测，但很可能是因为通常情况下，us-east-1地区比其他地区更早获得新功能，并且在确定命名约定的时候已经为了用户的稳定性而无法再更改us-east-1地区的命名方式。
英文:
This seems to just be an unimportant inconsistency between implementations in different regions.
The docs don't say why, so this sentence is a guess, but this is likely because us-east-1 usually gets new features before other regions, and by the time the naming convention was settled it was too late to change us-east-1 to match without potentially breaking things for users.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论