错误 - 在 AWS 上创建 Kubernetes 集群时出现“'unsupported architecture for instance type "t2.micro": i386'”
Error - '''unsupported architecture for instance type "t2.micro": i386''' while creating a Kubernetes Cluster on AWS
我是这个平台的新手，这是我的第二个问题。一个月以来，我一直在尝试使用 AWS 设置 Kubernetes 集群，但未成功。但是每天，我都会得到一个新的错误，但是这一次，我无法解决这个错误。
我在 Virtual Box 中使用 Kali Linux，Windows 作为主机。我正在按照 Udemy 的教程进行设置。
我已经成功安装了 Kops、Kubectl 和 AWSCli。
我已经使用 AWS configure 正确配置了密钥（出于学习目的，我已授予我的用户完全管理员权限）
我创建了 S3 存储桶（授予它 public 访问权限）
现在要创建托管区域，我使用了 AWS Route 53。
Here are specs of my hosted zone
因为我没有域，所以我从 freenom.com 购买了一个免费的子域并正确配置了名称服务器。
Free domain configuration
之后，我使用ssh-keygen创建了一对用于登录集群的密钥。
最后，我是运行这个命令，
kops create cluster --name=kubernetes.hellaswell.ml --state=s3://kops-state-crap --zones=eu-west-1a --node-count=2 --node-size=t2.micro --master-size=t2.micro --dns-zone=kubernetes.hellaswell.ml 1 ⚙
I0418 22:49:10.855151 12216 new_cluster.go:238] Inferred "aws" cloud provider from zone "eu-west-1a"
I0418 22:49:10.855313 12216 new_cluster.go:962] Cloud Provider ID = aws
I0418 22:49:12.604015 12216 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet eu-west-1a
unable to determine machine architecture for InstanceGroup "master-eu-west-1a": unsupported architecture for instance type "t2.micro": i386
unsupported architecture for instance type "t2.micro": i386
一些 EC2 t2.micro 实例实际上是 32 位机器。参见 How to find if my Amazon EC2 instance is 32 bit or 64 bit?。
您的 Kubernetes 容器可能包含为 64 位机器编译的二进制文件。我建议您选择不同的 EC2 实例类型，例如t3.small.
谢谢，https://whosebug.com/users/4523789/ole-markus-with，您使用 t3.medium 的建议确实很有帮助。
┌──(kali㉿kali)-[~]
└─$ kops create cluster --name=kube.hellaswell.ml --state=s3://kops-state-crap --zones=eu-west-1a --node-count=2 --node-size=t2.small --master-size=t2.small --dns-zone=kube.hellaswell.ml
I0419 20:18:36.700942 2086 new_cluster.go:238] Inferred "aws" cloud provider from zone "eu-west-1a"
I0419 20:18:36.700999 2086 new_cluster.go:962] Cloud Provider ID = aws
I0419 20:18:37.938892 2086 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet eu-west-1a
unable to determine machine architecture for InstanceGroup "master-eu-west-1a": unsupported architecture for instance type "t2.small": i386
┌──(kali㉿kali)-[~]
└─$ kops create cluster --name=kube.hellaswell.ml --state=s3://kops-state-crap --zones=eu-west-1a --node-count=2 --node-size=t2.medium --master-size=t2.medium --dns-zone=kube.hellaswell.ml 1 ⨯
I0419 20:18:58.255708 2094 new_cluster.go:238] Inferred "aws" cloud provider from zone "eu-west-1a"
I0419 20:18:58.255834 2094 new_cluster.go:962] Cloud Provider ID = aws
I0419 20:18:59.282307 2094 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet eu-west-1a
unable to determine machine architecture for InstanceGroup "master-eu-west-1a": unsupported architecture for instance type "t2.medium": i386
┌──(kali㉿kali)-[~]
└─$ kops create cluster --name=kube.hellaswell.ml --state=s3://kops-state-crap --zones=eu-west-1a --node-count=2 --node-size=t3.medium --master-size=t3.medium --dns-zone=kube.hellaswell.ml 1 ⨯
I0419 20:20:47.323068 2103 new_cluster.go:238] Inferred "aws" cloud provider from zone "eu-west-1a"
I0419 20:20:47.323286 2103 new_cluster.go:962] Cloud Provider ID = aws
I0419 20:20:49.012132 2103 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet eu-west-1a
I0419 20:20:51.943459 2103 create_cluster.go:726] Using SSH public key: /home/kali/.ssh/id_rsa.pub
Previewing changes that will be made:
I0419 20:21:03.446344 2103 executor.go:111] Tasks: 0 done / 77 total; 43 can run
W0419 20:21:05.094898 2103 vfs_castore.go:604] CA private key was not found
I0419 20:21:05.095112 2103 executor.go:111] Tasks: 43 done / 77 total; 16 can run
I0419 20:21:06.137672 2103 executor.go:111] Tasks: 59 done / 77 total; 16 can run
I0419 20:21:07.358255 2103 executor.go:111] Tasks: 75 done / 77 total; 2 can run
I0419 20:21:08.538778 2103 executor.go:111] Tasks: 77 done / 77 total; 0 can run
Will create resources:
AutoscalingGroup/master-eu-west-1a.masters.kube.hellaswell.ml
我是 AWS 和 Kubernetes 的新手，请原谅我的好奇心，但我想知道，其他人如何使用 t2.micro 创建集群。我也看过 Udemy 和这个博客上的教程 https://www.scottyfullstack.com/blog/setting-up-a-free-tier-kubernetes-cluster-with-kop/
如果有 64 位变量可用，kOps 现在应该支持这些实例类型。
我是这个平台的新手，这是我的第二个问题。一个月以来，我一直在尝试使用 AWS 设置 Kubernetes 集群，但未成功。但是每天，我都会得到一个新的错误，但是这一次，我无法解决这个错误。
我在 Virtual Box 中使用 Kali Linux，Windows 作为主机。我正在按照 Udemy 的教程进行设置。
我已经成功安装了 Kops、Kubectl 和 AWSCli。
我已经使用 AWS configure 正确配置了密钥（出于学习目的，我已授予我的用户完全管理员权限）
我创建了 S3 存储桶（授予它 public 访问权限）
现在要创建托管区域，我使用了 AWS Route 53。 Here are specs of my hosted zone
因为我没有域，所以我从 freenom.com 购买了一个免费的子域并正确配置了名称服务器。 Free domain configuration
之后，我使用ssh-keygen创建了一对用于登录集群的密钥。
最后，我是运行这个命令，
kops create cluster --name=kubernetes.hellaswell.ml --state=s3://kops-state-crap --zones=eu-west-1a --node-count=2 --node-size=t2.micro --master-size=t2.micro --dns-zone=kubernetes.hellaswell.ml 1 ⚙
I0418 22:49:10.855151 12216 new_cluster.go:238] Inferred "aws" cloud provider from zone "eu-west-1a"
I0418 22:49:10.855313 12216 new_cluster.go:962] Cloud Provider ID = aws
I0418 22:49:12.604015 12216 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet eu-west-1a
unable to determine machine architecture for InstanceGroup "master-eu-west-1a": unsupported architecture for instance type "t2.micro": i386
unsupported architecture for instance type "t2.micro": i386
一些 EC2 t2.micro 实例实际上是 32 位机器。参见 How to find if my Amazon EC2 instance is 32 bit or 64 bit?。
您的 Kubernetes 容器可能包含为 64 位机器编译的二进制文件。我建议您选择不同的 EC2 实例类型，例如t3.small.
谢谢，https://whosebug.com/users/4523789/ole-markus-with，您使用 t3.medium 的建议确实很有帮助。
┌──(kali㉿kali)-[~]
└─$ kops create cluster --name=kube.hellaswell.ml --state=s3://kops-state-crap --zones=eu-west-1a --node-count=2 --node-size=t2.small --master-size=t2.small --dns-zone=kube.hellaswell.ml
I0419 20:18:36.700942 2086 new_cluster.go:238] Inferred "aws" cloud provider from zone "eu-west-1a"
I0419 20:18:36.700999 2086 new_cluster.go:962] Cloud Provider ID = aws
I0419 20:18:37.938892 2086 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet eu-west-1a
unable to determine machine architecture for InstanceGroup "master-eu-west-1a": unsupported architecture for instance type "t2.small": i386
┌──(kali㉿kali)-[~]
└─$ kops create cluster --name=kube.hellaswell.ml --state=s3://kops-state-crap --zones=eu-west-1a --node-count=2 --node-size=t2.medium --master-size=t2.medium --dns-zone=kube.hellaswell.ml 1 ⨯
I0419 20:18:58.255708 2094 new_cluster.go:238] Inferred "aws" cloud provider from zone "eu-west-1a"
I0419 20:18:58.255834 2094 new_cluster.go:962] Cloud Provider ID = aws
I0419 20:18:59.282307 2094 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet eu-west-1a
unable to determine machine architecture for InstanceGroup "master-eu-west-1a": unsupported architecture for instance type "t2.medium": i386
┌──(kali㉿kali)-[~]
└─$ kops create cluster --name=kube.hellaswell.ml --state=s3://kops-state-crap --zones=eu-west-1a --node-count=2 --node-size=t3.medium --master-size=t3.medium --dns-zone=kube.hellaswell.ml 1 ⨯
I0419 20:20:47.323068 2103 new_cluster.go:238] Inferred "aws" cloud provider from zone "eu-west-1a"
I0419 20:20:47.323286 2103 new_cluster.go:962] Cloud Provider ID = aws
I0419 20:20:49.012132 2103 subnets.go:180] Assigned CIDR 172.20.32.0/19 to subnet eu-west-1a
I0419 20:20:51.943459 2103 create_cluster.go:726] Using SSH public key: /home/kali/.ssh/id_rsa.pub
Previewing changes that will be made:
I0419 20:21:03.446344 2103 executor.go:111] Tasks: 0 done / 77 total; 43 can run
W0419 20:21:05.094898 2103 vfs_castore.go:604] CA private key was not found
I0419 20:21:05.095112 2103 executor.go:111] Tasks: 43 done / 77 total; 16 can run
I0419 20:21:06.137672 2103 executor.go:111] Tasks: 59 done / 77 total; 16 can run
I0419 20:21:07.358255 2103 executor.go:111] Tasks: 75 done / 77 total; 2 can run
I0419 20:21:08.538778 2103 executor.go:111] Tasks: 77 done / 77 total; 0 can run
Will create resources:
AutoscalingGroup/master-eu-west-1a.masters.kube.hellaswell.ml
我是 AWS 和 Kubernetes 的新手，请原谅我的好奇心，但我想知道，其他人如何使用 t2.micro 创建集群。我也看过 Udemy 和这个博客上的教程 https://www.scottyfullstack.com/blog/setting-up-a-free-tier-kubernetes-cluster-with-kop/
如果有 64 位变量可用，kOps 现在应该支持这些实例类型。