时间戳

首页 > 解决方案 > AWS EKS 留言簿 URL 无法访问

amazon-web-services - AWS EKS 留言簿 URL 无法访问

问题描述

我在 Win10 上使用 cygwin 和其他一些 choco 东西，一切都已安装并运行良好。我能够从 ecs-cli 和 fargate 教程安装和运行东西，也可以编写。

现在我正在尝试 EKS 并在此处从 ekstcl 入门设置集群和留言簿： https ://docs.aws.amazon.com/eks/latest/userguide/getting-started-eksctl.html

然后在此处设置集群后： https ://docs.aws.amazon.com/eks/latest/userguide/eks-guestbook.html

我创建了 AWS Fargate-only 集群。我只是一步一步地跟着，最后当我在浏览器中打开它说的网址时

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

现在我打开这个： http ://a8b3bb2e121f511ea82cb1294ea943ee-1408939369.us-east-1.elb.amazonaws.com:3000

一无所获:(

我究竟做错了什么？

标签： amazon-web-servicesamazon-eksaws-fargate

解决方案

你没有做错什么。但是，在 Fargate 上使用 EKS 时，您必须考虑某些事项。这包括在撰写本文时仅支持 ALB。留言簿示例使用服务类型LoadBalancer，导致创建经典负载均衡器，即 ATM，在 Fargate 上的 EKS 中不支持。

推荐阅读