Amazon web services AWS EKS留言簿url不可访问
我在Win10上使用cygwin和其他一些choco东西,所有东西都已安装并运行良好。我能够安装和运行ecs cli和fargate教程中的内容,也可以编写 现在,我正在尝试EKS,并在ekstcl入门中设置集群和来宾手册: 然后在此处设置集群后: 我创建了AWS Fargate only集群。 我只是一步一步地跟着,最后在浏览器中打开url时,它会这样说Amazon web services AWS EKS留言簿url不可访问,amazon-web-services,amazon-eks,aws-fargate,Amazon Web Services,Amazon Eks,Aws Fargate,我在Win10上使用cygwin和其他一些choco东西,所有东西都已安装并运行良好。我能够安装和运行ecs cli和fargate教程中的内容,也可以编写 现在,我正在尝试EKS,并在ekstcl入门中设置集群和来宾手册: 然后在此处设置集群后: 我创建了AWS Fargate only集群。 我只是一步一步地跟着,最后在浏览器中打开url时,它会这样说 This page isn’t working a8b3bb2e121f511ea82cb1294ea943ee-1408939369.
This page isn’t working
a8b3bb2e121f511ea82cb1294ea943ee-1408939369.us-east-1.elb.amazonaws.com didn’t send any data.
ERR_EMPTY_RESPONSE
逐步:
$ eksctl version
[ℹ] version.Info{BuiltAt:"", GitCommit:"", GitTag:"0.11.1"}
$ eksctl create cluster --name eks-snafu --version 1.14 --region us-east-1 --fargate
[ℹ] eksctl version 0.11.1
[ℹ] using region us-east-1
[ℹ] setting availability zones to [us-east-1f us-east-1b]
[ℹ] subnets for us-east-1f - public:192.168.0.0/19 private:192.168.64.0/19
[ℹ] subnets for us-east-1b - public:192.168.32.0/19 private:192.168.96.0/19
[ℹ] using Kubernetes version 1.14
[ℹ] creating EKS cluster "eks-snafu" in "us-east-1" region with Fargate profile
[ℹ] if you encounter any issues, check CloudFormation console or try 'eksctl utils describe-stacks --region=us-east-1 --cluster=eks-snafu'
[ℹ] CloudWatch logging will not be enabled for cluster "eks-snafu" in "us-east-1"
[ℹ] you can enable it with 'eksctl utils update-cluster-logging --region=us-east-1 --cluster=eks-snafu'
[ℹ] Kubernetes API endpoint access will use default of {publicAccess=true, privateAccess=false} for cluster "eks-snafu" in "us-east-1"
[ℹ] 1 task: { create cluster control plane "eks-snafu" }
[ℹ] building cluster stack "eksctl-eks-snafu-cluster"
[ℹ] deploying stack "eksctl-eks-snafu-cluster"
[✔] all EKS cluster resources for "eks-snafu" have been created
[✔] saved kubeconfig as "<MY WIN HOME>/.kube/config"
[ℹ] creating Fargate profile "fp-default" on EKS cluster "eks-snafu"
[ℹ] created Fargate profile "fp-default" on EKS cluster "eks-snafu"
[ℹ] "coredns" is now schedulable onto Fargate
[ℹ] "coredns" is now scheduled onto Fargate
[ℹ] "coredns" pods are now scheduled onto Fargate
[ℹ] kubectl command should work with "<MY WIN HOME>/.kube/config", try 'kubectl get nodes'
[✔] EKS cluster "eks-snafu" in "us-east-1" region is ready
$ kubectl get svc -o wide
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
kubernetes ClusterIP 10.100.0.1 <none> 443/TCP 7m7s <none>
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/redis-master-controller.json
replicationcontroller/redis-master created
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/redis-master-service.json
service/redis-master created
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/redis-slave-controller.json
replicationcontroller/redis-slave created
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/redis-slave-service.json
service/redis-slave created
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/guestbook-controller.json
replicationcontroller/guestbook created
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/guestbook-service.json
service/guestbook created
$ kubectl get services -o wide
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
guestbook LoadBalancer 10.100.201.159 a8b3bb2e121f511ea82cb1294ea943ee-1408939369.us-east-1.elb.amazonaws.com 3000:32600/TCP 12s app=guestbook
kubernetes ClusterIP 10.100.0.1 <none> 443/TCP 14m <none>
redis-master ClusterIP 10.100.133.248 <none> 6379/TCP 43s app=redis,role=master
redis-slave ClusterIP 10.100.198.154 <none> 6379/TCP 26s app=redis,role=slave
$eksctl版本
[ℹ] version.Info{BuiltAt:,GitCommit:,GitTag:“0.11.1”}
$eksctl创建集群——名称eks snafu——版本1.14——地区us-east-1——fargate
[ℹ] eksctl版本0.11.1
[ℹ] 使用区域us-east-1
[ℹ] 将可用区设置为[us-east-1f us-east-1b]
[ℹ] us-east-1f子网-公共:192.168.0.0/19私人:192.168.64.0/19
[ℹ] us-east-1b的子网-公用:192.168.32.0/19专用:192.168.96.0/19
[ℹ] 使用Kubernetes 1.14版
[ℹ] 利用Fargate剖面在“us-east-1”区域创建EKS集群“EKS snafu”
[ℹ] 如果遇到任何问题,请检查CloudFormation控制台或尝试“eksctl utils descripe stacks--region=us-east-1--cluster=eks snafu”
[ℹ] “us-east-1”中的群集“eks snafu”将不启用CloudWatch日志记录
[ℹ] 您可以使用“eksctl utils更新集群日志记录--region=us-east-1--cluster=eks snafu”来启用它
[ℹ] Kubernetes API端点访问将对“us-east-1”中的集群“eks snafu”使用默认值{publicAccess=true,privateAccess=false}
[ℹ] 1任务:{创建群集控制平面“eks snafu”}
[ℹ] 构建集群堆栈“eksctl eks snafu集群”
[ℹ] 部署堆栈“eksctl eks snafu群集”
[✔] 已为“EKS snafu”创建了所有EKS群集资源
[✔] 已将kubeconfig保存为“/.kube/config”
[ℹ] 在EKS群集“EKS snafu”上创建Fargate配置文件“fp default”
[ℹ] 在EKS群集“EKS snafu”上创建了Fargate配置文件“fp default”
[ℹ] “coredns”现在可调度到Fargate
[ℹ] “coredns”现在被安排在Fargate上
[ℹ] “coredns”吊舱现在被安排在Fargate上
[ℹ] kubectl命令应与“/.kube/config”一起使用,请尝试“kubectl获取节点”
[✔] “us-east-1”地区的EKS集群“EKS snafu”已准备就绪
$kubectl获得svc-o宽
名称类型CLUSTER-IP外部IP端口年龄选择器
kubernetes ClusterIP 10.100.0.1 443/TCP 7m7s
$kubectl适用-fhttps://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/redis-master-controller.json
已创建replicationcontroller/redis主机
$kubectl适用-fhttps://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/redis-master-service.json
已创建服务/redis主机
$kubectl适用-fhttps://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/redis-slave-controller.json
已创建replicationcontroller/redis从机
$kubectl适用-fhttps://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/redis-slave-service.json
已创建服务/redis从服务器
$kubectl适用-fhttps://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/guestbook-controller.json
已创建复制控制器/留言簿
$kubectl适用-fhttps://raw.githubusercontent.com/kubernetes/examples/master/guestbook-go/guestbook-service.json
已创建服务/留言簿
$kubectl获得服务-全世界
名称类型CLUSTER-IP外部IP端口年龄选择器
留言簿负载平衡器10.100.201.159 A8B3BB2E121F51EA82CB1294EA943EE-1408939369.us-east-1.elb.amazonaws.com 3000:32600/TCP 12s app=guestbook
kubernetes ClusterIP 10.100.0.1 443/TCP 14m
redis主群集IP 10.100.133.248 6379/TCP 43s应用程序=redis,角色=主群集
redis从集群IP 10.100.198.154 6379/TCP 26s app=redis,角色=slave
现在我打开这个:
什么也得不到:(
我做错了什么?你没有做错任何事。但是,在Fargate上使用EKS时,你必须做某些事情。这包括,在撰写本文时,仅支持ALB。留言簿示例是服务类型
负载平衡器
,导致创建了一个经典的负载平衡器,即ATM,在F上的EKS中不受支持argate.Michael Hausenblas是正确的:留言簿示例不适用于fargate集群
要设置仅限Linux的群集,可以按照链接()页面中的说明进行操作。在“创建Amazon EKS群集和工作节点”时,只需选择“仅限Linux工作负载的群集”而不是“仅限AWS Fargate群集”。为了方便起见,我复制了下面的命令
创建集群\
--产品名称\
--地区代码\
--节点组名称标准工作者\
--节点类型t3.1中等\
--节点3\
--最小节点数1\
--节点最多4个\
--ssh访问\
--ssh公钥my-public-key.pub\
--管理
注意,这个问题已经提出几个月了,并且被标记为已接受,但我也有同样的问题,并且我认为其他初学者可能需要更明确的说明
顺便说一句,这可能是一个更好的评论,但我还没有足够的声誉来评论!谢谢Michael!运行此示例需要做些什么?我对这些东西非常陌生,还有很多东西需要学习。不幸的是,除非您使用Ingress资源,否则此示例无法工作。我建议您从中选择一些内容(不使用CLB或持久卷)。