【问题标题】:How to connect to an EKS service from outside the cluster using a LoadBalancer in a private VPC如何使用私有 VPC 中的 LoadBalancer 从集群外部连接到 EKS 服务
【发布时间】:2021-05-30 01:43:42
【问题描述】:

我正在尝试在同一 VPC 内的集群外部公开 Kafka 的 EKS 部署。

在 terraform 中,我为 Kafka 安全组添加了一个入口规则:

  ingress {
    from_port = 9092

    protocol = "tcp"
    to_port = 9092

    cidr_blocks = [
      "10.0.0.0/16",
    ]
  }

这是服务 yaml

apiVersion: v1
kind: Service
metadata:
  name: bootstrap-external
  namespace: kafka
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-internal: "10.0.0.0/16"
    service.beta.kubernetes.io/aws-load-balancer-extra-security-groups: "sg-0....d,sg-0db....ae"
spec:
  type: LoadBalancer
  ports:
    - protocol: TCP
      port: 9092
      targetPort: 9092
  selector:
    app: kafka

当尝试从另一个实例连接时,属于 yaml 中的一个安全组, 我似乎能够通过负载均衡器建立连接,但没有被引用到 Kafka:

[ec2-user@ip-10-0-4-47 kafkacat]$ nc -zvw10 internal-a08....628f-1654182718.us-east-2.elb.amazonaws.com 9092
Ncat: Version 7.50 ( https://nmap.org/ncat )
Ncat: Connected to 10.0.3.151:9092.
Ncat: 0 bytes sent, 0 bytes received in 0.05 seconds.
[ec2-user@ip-10-0-4-47 kafkacat]$ nmap -Pn internal-a0837....a0e628f-1654182718.us-east-2.elb.amazonaws.com -p 9092

Starting Nmap 6.40 ( http://nmap.org ) at 2021-02-28 07:19 UTC
Nmap scan report for internal-a083747ab.....8f-1654182718.us-east-2.elb.amazonaws.com (10.0.2.41)
Host is up (0.00088s latency).
Other addresses for internal-a083747ab....36f0a0e628f-1654182718.us-east-2.elb.amazonaws.com (not scanned): 10.0.3.151 10.0.1.85
rDNS record for 10.0.2.41: ip-10-0-2-41.us-east-2.compute.internal
PORT     STATE SERVICE
9092/tcp open  unknown

Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds
[ec2-user@ip-10-0-4-47 kafkacat]$ kafkacat -b internal-a083747abf4....-1654182718.us-east-2.elb.amazonaws.com:9092 -t models
% Auto-selecting Consumer mode (use -P or -C to override)
% ERROR: Local: Host resolution failure: kafka-2.broker.kafka.svc.cluster.local:9092/2: Failed to resolve 'kafka-2.broker.kafka.svc.cluster.local:9092': Name or service not known
% ERROR: Local: Host resolution failure: kafka-1.broker.kafka.svc.cluster.local:9092/1: Failed to resolve 'kafka-1.broker.kafka.svc.cluster.local:9092': Name or service not known
% ERROR: Local: Host resolution failure: kafka-0.broker.kafka.svc.cluster.local:9092/0: Failed to resolve 'kafka-0.broker.kafka.svc.cluster.local:9092': Name or service not known
^C[ec2-user@ip-10-0-4-47 kafkacat]$

``

【问题讨论】:

    标签: amazon-web-services kubernetes amazon-vpc amazon-eks


    【解决方案1】:

    我们通过以下方式解决了 Kafka 连接:

    1. 向 Kafka 工作人员安全组添加入口规则(我们使用 Terraform)
      ingress {
        from_port = 9094
    
        protocol = "tcp"
        to_port = 9094
    
        cidr_blocks = [
          "10.0.0.0/16",
        ]
      }
    
    1. 在 Kubernetes YAML 中为每个代理配置负载均衡器服务(请注意,nodePort 中的最后一位数字对应于代理状态集 ID)。
    apiVersion: v1
    kind: Service
    metadata: 
      name: bootstrap-external-0
      namespace: kafka
      annotations: 
        service.beta.kubernetes.io/aws-load-balancer-internal: "10.0.0.0/16"
        service.beta.kubernetes.io/aws-load-balancer-extra-security-groups: sg-....d,sg-0db14....e,sg-001ce.....e,sg-0fe....15d13c
    spec: 
      type: LoadBalancer
      ports:
        - 
          protocol: TCP
          targetPort: 9094
          port: 32400
          nodePort: 32400
      selector: 
        app: kafka
        kafka-broker-id: "0"
    
    1. 通过解析kubctl -n kafka get svc bootstrap-external-0检索负载均衡器名称。
    2. 使用 Route 53 按约定添加 DNS 名称。
    3. 我们计划在创建负载平衡器后通过对 Route53 进行地形改造来实现自动化。

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 2021-01-20
      • 2023-02-09
      • 2022-12-12
      • 2021-02-08
      • 1970-01-01
      • 2020-11-24
      • 2016-08-27
      • 1970-01-01
      相关资源
      最近更新 更多