尝试在Amazon EKS中从AWS经典负载均衡器转换为应用程序负载均衡器

时间：2020-08-18 20:01:21

标签： kubernetes amazon-eks aws-eks

我可以使用经典的负载均衡器来完成所有工作。我现在想更新我的Kubernetes环境，以使用应用程序负载平衡器代替传统的负载平衡器。我已经尝试了一些教程，但到目前为止还没有运气。部署后，我仍然收到503错误。

我在eksctl上启动了集群，然后在本教程https://docs.aws.amazon.com/eks/latest/userguide/alb-ingress.html中安装并运行了示例应用程序。我确实建立了一个ALB，并且按照本教程中概述的示例应用程序的要求进行了所有工作。我尝试为我的环境修改YAML以使用ALB并不断收到503错误。我不确定接下来要尝试什么。 我怀疑我的问题可能是我将Nginx和我的应用程序放在同一个容器中（如果可能，我希望将其保留）。

这是我为更新应用程序而试图使ALB正常运行的YAML：

kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-config
data:
  nginx.conf: |
    events {
    }
    http {
    include    /etc/nginx/mime.types;
      server {
        listen 80 default_server;
        listen [::]:80 default_server;
        server_name test-ggg.com www.test-ggg.com;
        if ($http_x_forwarded_proto = "http") {
          return 301 https://$server_name$request_uri;
        }
        root /var/www/html;
        index index.php index.html;
        location static {
          alias /var/www/html;
        }
        error_log  /var/log/nginx/error.log;
        access_log /var/log/nginx/access.log;
        location ~ \.php$ {
          fastcgi_split_path_info ^(.+\.php)(/.+)$;
          fastcgi_pass 127.0.0.1:9000;
          fastcgi_index index.php;
          include fastcgi_params;
          fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
          fastcgi_param PATH_INFO $fastcgi_path_info;
        }
        location / {
          try_files $uri $uri/ /index.php?$query_string;
          gzip_static on;
        }
      }
    }
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: deployment
  labels:
    name: deployment
spec:
  replicas: 1
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 2
  selector:
    matchLabels:
      name: templated-pod
  template:
    metadata:
      name: deployment-template
      labels:
        name: templated-pod
    spec:
      volumes:
        - name: app-files
          emptyDir: {}
        - name: nginx-config-volume
          configMap:
            name: nginx-config
      containers:
        - image:  xxxxxxx.dkr.ecr.us-east-2.amazonaws.com/test:4713
          name: app
          volumeMounts:
            - name: app-files
              mountPath: /var/www/html
          lifecycle:
            postStart:
              exec:
                command: ["/bin/sh", "-c", "cp -r /var/www/public/. /var/www/html"]
          resources:
            limits:
              cpu: 100m
            requests:
              cpu: 50m
        - image: nginx:alpine
          name: nginx
          volumeMounts:
            - name: app-files
              mountPath: /var/www/html
            - name: nginx-config-volume
              mountPath: /etc/nginx/nginx.conf
              subPath: nginx.conf
          resources:
            limits:
              cpu: 100m
            requests:
              cpu: 50m
          ports:
          - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: "service-alb"
  namespace: default
  annotations:
    alb.ingress.kubernetes.io/target-group-attributes: slow_start.duration_seconds=45
    alb.ingress.kubernetes.io/healthcheck-interval-seconds: '5'
    alb.ingress.kubernetes.io/healthcheck-timeout-seconds: '2'
    alb.ingress.kubernetes.io/healthy-threshold-count: '2'
    alb.ingress.kubernetes.io/unhealthy-threshold-count: '3'
spec:
  ports:
    - port: 80
      targetPort: 80
      name: http
  type: NodePort
  selector:
    app: templated-pod
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: app-ingress
  namespace: default
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/target-type: ip
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/certificate-arn: arn:aws:acm:us-east-2:dddddddd:certificate/f61c2837-484c-ddddddddd-bab7c4d4452c
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
    alb.ingress.kubernetes.io/actions.ssl-redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'
  labels:
    app: app-ingress
spec:
  rules:
  - host: test-ggg.com
    http:
      paths:
      - backend:
          serviceName: "service-alb"
          servicePort: 80
        path: /*

这是具有经典负载均衡器的Yaml。当我使用此功能时，一切正常：

kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-config
data:
  nginx.conf: |
    events {
    }
    http {
    include    /etc/nginx/mime.types;
      server {
        listen 80 default_server;
        listen [::]:80 default_server;
        server_name test-ggg.com www.test-ggg.com;
        if ($http_x_forwarded_proto = "http") {
          return 301 https://$server_name$request_uri;
        }
        root /var/www/html;
        index index.php index.html;
        location static {
          alias /var/www/html;
        }
        error_log  /var/log/nginx/error.log;
        access_log /var/log/nginx/access.log;
        location ~ \.php$ {
          fastcgi_split_path_info ^(.+\.php)(/.+)$;
          fastcgi_pass 127.0.0.1:9000;
          fastcgi_index index.php;
          include fastcgi_params;
          fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
          fastcgi_param PATH_INFO $fastcgi_path_info;
        }
        location / {
          try_files $uri $uri/ /index.php?$query_string;
          gzip_static on;
        }
      }
    }
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: deployment
  labels:
    name: deployment
spec:
  replicas: 1
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1
      maxUnavailable: 2
  selector:
    matchLabels:
      name: templated-pod
  template:
    metadata:
      name: deployment-template
      labels:
        name: templated-pod
    spec:
      volumes:
        - name: app-files
          emptyDir: {}
        - name: nginx-config-volume
          configMap:
            name: nginx-config
      containers:
        - image:  99ddddddddd.dkr.ecr.us-east-2.amazonaws.com/test:4713
          name: app
          volumeMounts:
            - name: app-files
              mountPath: /var/www/html
          lifecycle:
            postStart:
              exec:
                command: ["/bin/sh", "-c", "cp -r /var/www/public/. /var/www/html"]
          resources:
            limits:
              cpu: 100m
            requests:
              cpu: 50m
        - image: nginx:alpine
          name: nginx
          volumeMounts:
            - name: app-files
              mountPath: /var/www/html
            - name: nginx-config-volume
              mountPath: /etc/nginx/nginx.conf
              subPath: nginx.conf
          resources:
            limits:
              cpu: 100m
            requests:
              cpu: 50m
          ports:
          - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: service-loadbalancer
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "http"
    service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "https"
    service.beta.kubernetes.io/aws-load-balancer-ssl-cert:  arn:aws:acm:us-east-2:dddddddd:certificate/f61c2837-484c-4fac-a26c-dddddddd4452c
spec:
  selector:
    name: templated-pod
  ports:
    - name: http
      port: 80
      targetPort: 80
    - name: https
      port: 443
      targetPort: 80
  type: LoadBalancer

1 个答案:

答案 0 :(得分：0)

在获得一些教程帮助之后，我了解了有关服务，选择器和pod命名的更多信息！ （很棒的教程-https://www.youtube.com/watch?v=sGZx3OjMPQI）

我将豆荚命名为-“名称：templated-pod” 我让服务中的选择器在寻找：

  selector:
    app: templated-pod

无法建立连接！

我将选择器更改为以下选项，它起作用了：

  selector:
    name: templated-pod

希望这对其他人有帮助！

相关问题
最新问题