amazon-web-services - 如何加入 ALB 入口组而不是覆盖 EKS 中的现有入口组？

Question

我正在将 K8S 部署到 AWS EKS 集群并使用 ALB 进行部署。我想将一个 ALB 用于多个服务，但我不知道如何共享同一个 ALB。每次我部署一个入口时，它都会覆盖现有的入口。
我有两个配置 yaml 文件:
一个.yaml

---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: sample-ingress
  namespace: default
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/group.name: sample-ingress
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/target-type: ip
    alb.ingress.kubernetes.io/group.order: '1'
spec:
  rules:
    - http:
        paths:
          - path: /sample-app/*
            backend:
              serviceName: sample-entrypoint
              servicePort: 80

b.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: sample-ingress
  namespace: default
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/group.name: sample-ingress
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/target-type: ip
    alb.ingress.kubernetes.io/group.order: '2'
spec:
  rules:
    - http:
        paths:
          - path: /sample-es/*
            backend:
              serviceName: sample-es-entrypoint
              servicePort: 9200

我希望两者共享相同的 ALB，因此我将组名指定为相同: alb.ingress.kubernetes.io/group.name: sample-ingress我还在两个文件中指定了不同的顺序。
但是当我运行时 kubectl apply -f a.yaml , 它使用我在配置文件中指定的规则创建一个 ALB: /sample-app/* .但是当我运行 kubectl apply -f b.yaml ，它会用 /sample-es/* 覆盖现有规则.那么我怎样才能让两者共享相同的 ALB 并允许它们提供不同的规则呢？

Answer 1

我想您可以创建单独的入口并将它们附加到相同的服务配置。用 alb 指向服务配置，这应该可以工作。我有一个面向内部服务的配置，请看看这是否适合您。

apiVersion: v1
kind: Service
metadata:
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
  labels:
    app.kubernetes.io/instance: goldendev-ingress-test
    app.kubernetes.io/managed-by: Tiller
    app.kubernetes.io/name: ingress-test
    environment: DEV
    helm.sh/chart: ingress-test
  name: ingress-test
  namespace: default
spec:
  externalTrafficPolicy: Cluster
  ports:
  - name: http
    port: 80
    protocol: TCP
    targetPort: 8080
  selector:
    app.kubernetes.io/instance: z1
    app.kubernetes.io/name: gunicorn
  sessionAffinity: None
  type: LoadBalancer

入口.yaml

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: sample-ingress
  namespace: default
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/group.name: sample-ingress
    alb.ingress.kubernetes.io/scheme: internal
    alb.ingress.kubernetes.io/target-type: ip
    alb.ingress.kubernetes.io/group.order: '1'
spec:
  rules:
    - http:
        paths:
          - path: /mappings/v1/hello/*
            backend:
              serviceName: ingress-test
              servicePort: 80
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: sample-ingress-1
  namespace: default
  annotations:
    kubernetes.io/ingress.class: alb
    alb.ingress.kubernetes.io/group.name: sample-ingress
    alb.ingress.kubernetes.io/scheme: internal
    alb.ingress.kubernetes.io/target-type: ip
    alb.ingress.kubernetes.io/group.order: '2'
spec:
  rules:
    - http:
        paths:
          - path: /mappings/v1/teams/*
            backend:
              serviceName: ingress-test-2
              servicePort: 80

我在 AWS 控制台中进行了验证，它仅创建了 1 个具有服务配置的负载均衡器。
入口列表:

 kubectl get ingress
NAME               HOSTS   ADDRESS   PORTS   AGE
sample-ingress     *                 80      19m
sample-ingress-1   *                 80      19m

如果这有帮助，请告诉我。