Amazon web services 错误-''';实例类型“的不支持体系结构”;t2.微“:i386''';在AWS上创建Kubernetes群集时
我是这个平台的新手,这是我的第二个问题。一个月来,我一直在尝试使用AWS建立Kubernetes群集,但没有成功。但是每天,我都会遇到一个新的错误,但这次,我无法解决这个错误 我在虚拟机中使用Kali Linux,并以Windows作为主机。我正在按照Udemy的教程进行设置Amazon web services 错误-''';实例类型“的不支持体系结构”;t2.微“:i386''';在AWS上创建Kubernetes群集时,amazon-web-services,kubernetes,aws-cli,kubectl,kops,Amazon Web Services,Kubernetes,Aws Cli,Kubectl,Kops,我是这个平台的新手,这是我的第二个问题。一个月来,我一直在尝试使用AWS建立Kubernetes群集,但没有成功。但是每天,我都会遇到一个新的错误,但这次,我无法解决这个错误 我在虚拟机中使用Kali Linux,并以Windows作为主机。我正在按照Udemy的教程进行设置 我已成功安装了Kops、Kubectl和AWSCli 我已使用AWS配置正确配置密钥(出于学习目的,我已授予我的用户完全管理员权限) 我创建了S3存储桶(为其提供了公共访问权限) 现在,为了创建托管区域,我使用了AW
┌──(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和这个博客上也看到了教程谢谢你,你关于使用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和这个博客上也看到了教程你在用什么AMI?我在用Kali Linux访问AWS和配置集群。关于AMI,是t2.micro。(很抱歉,但我认为这就是我在“kops create cluster”命令中提到的图像。否则,我不知道我们也必须在其他地方指定它)。我不建议低于默认实例类型(目前为t3.medium)。您很可能会遇到无法适应基本工作负载或反应非常缓慢的集群。此外,如果你一直苦苦挣扎长达一个月,你可以考虑加入KOP松弛通道来更快的反馈循环。你使用的是什么AMI?我使用的是KALI Linux,我正在访问AWS并配置我的集群。关于AMI,是t2.micro。(很抱歉,但我认为这就是我在“kops create cluster”命令中提到的图像。否则,我不知道我们也必须在其他地方指定它)。我不建议低于默认实例类型(目前为t3.medium)。您很可能会遇到无法适应基本工作负载或反应非常缓慢的集群。此外,如果你已经苦苦挣扎长达一个月,你可以考虑加入KOP松弛通道来更快的反馈循环。但是在KOPS创建集群命令中,没有选择指定64位或32位的选项。我将在命令中使用t3.small,如果它有效,我将更新您。kOps二进制文件仅为64位。没有可用的32位二进制文件。t3.small不工作。它给出了相同的错误。但是在kops create cluster命令中,没有指定64位或32位的选项。我将在命令中使用t3.small,如果它有效,我将更新您。kOps二进制文件仅为64位。没有可用的32位二进制文件。t3.small不工作。它给出了同样的错误。