如何在 Kafka 连接器中正确连接 Elastic Operator 部署的 Elasticsearch?

Posted

技术标签:

【中文标题】如何在 Kafka 连接器中正确连接 Elastic Operator 部署的 Elasticsearch?【英文标题】:How to connect Elasticsearch deployed by Elastic Operator correctly in a Kafka connector? 【发布时间】:2022-01-12 23:03:06 【问题描述】:

我在 Kafka 中有一些 CDC 数据。现在我正试图从 Kafka 下沉到 Elasticsearch。这是我到目前为止所做的:

第 1 步 - 在 Kubernetes 中部署 Elasticsearch(成功)

我按照本教程使用 Elastic Operator 在 Kubernetes 中部署了 Elasticsearch:

    在您的 Kubernetes 集群中部署 ECK:https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-deploy-eck.html 部署 Elasticsearch 集群:https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-deploy-elasticsearch.html
apiVersion: elasticsearch.k8s.elastic.co/v1
kind: Elasticsearch
metadata:
  name: hm-elasticsearch
  namespace: elastic
spec:
  version: 7.14.0
  nodeSets:
    - name: default
      count: 1
      config:
        node.store.allow_mmap: false

根据教程,我可以通过在标题中提供用户名elastic和密码passw0rd来成功调用

curl -u "elastic:passw0rd" -k "https://hm-elasticsearch-es-http.elastic:9200"

返回


    "name": "hm-elasticsearch-es-default-0",
    "cluster_name": "hm-elasticsearch",
    "cluster_uuid": "TWgIk0YGR_GVr7IJZcW62g",
    "version": 
        "number": "7.14.0",
        "build_flavor": "default",
        "build_type": "docker",
        "build_hash": "dd5a0a2acaa2045ff9624f3729fc8a6f40835aa1",
        "build_date": "2021-07-29T20:49:32.864135063Z",
        "build_snapshot": false,
        "lucene_version": "8.9.0",
        "minimum_wire_compatibility_version": "6.8.0",
        "minimum_index_compatibility_version": "6.0.0-beta1"
    ,
    "tagline": "You Know, for Search"

第 2 步 - 添加 ElasticsearchSinkConnector(连接 Elasticsearch 失败)

现在我正在尝试添加 ElasticsearchSinkConnector,但是我在设置它时遇到了问题。

我看到了How to Kafka Connect Elasticsearch with SSL?。 Elastic Cloud 只需要传递用户名和密码。所以我想它会和我的相似。

另外,基于this ElasticsearchSinkConnector config,我写了我的配置,然后尝试通过验证

curl --location --request PUT 'http://hm-connect-cluster-connect-api.kafka:8083/connector-plugins/io.confluent.connect.elasticsearch.ElasticsearchSinkConnector/config/validate' \
--header 'Content-Type: application/json' \
--data-raw '
    "name": "elasticsearch-sink",
    "connector.class": "io.confluent.connect.elasticsearch.ElasticsearchSinkConnector",
    "tasks.max": "1",
    "topics": "opa_db_server.public.roles",
    "connection.url": "https://hm-elasticsearch-es-http.elastic:9200",
    "connection.username": "elastic",
    "connection.password": "passw0rd",
    "transforms": "unwrap,key",
    "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState",
    "transforms.unwrap.drop.tombstones": "false",
    "transforms.key.type": "org.apache.kafka.connect.transforms.ExtractField$Key",
    "transforms.key.field": "role_id",
    "key.ignore": "false",
    "behavior.on.null.values": "delete"
'

返回错误


    "name": "io.confluent.connect.elasticsearch.ElasticsearchSinkConnector",
    "error_count": 3,
    "groups": [
        "Common",
        "Transforms",
        "Predicates",
        "Error Handling",
        "Transforms: unwrap",
        "Transforms: key",
        "Connector",
        "Data Conversion",
        "Proxy",
        "Security",
        "Kerberos",
        "Data Stream"
    ],
    "configs": [
        // ...
        
            "definition": 
                "name": "connection.url",
                "type": "LIST",
                "required": true,
                "default_value": null,
                "importance": "HIGH",
                "documentation": "The comma-separated list of one or more Elasticsearch URLs, such as ``http://eshost1:9200,http://eshost2:9200`` or ``https://eshost3:9200``. HTTPS is used for all connections if any of the URLs starts with ``https:``. A URL without a protocol is treated as ``http``.",
                "group": "Connector",
                "width": "LONG",
                "display_name": "Connection URLs",
                "dependents": [],
                "order": 1
            ,
            "value": 
                "name": "connection.url",
                "value": "https://hm-elasticsearch-es-http.elastic:9200",
                "recommended_values": [],
                "errors": [
                    "Could not connect to Elasticsearch. Error message: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target"
                ],
                "visible": true
            
        ,
        
            "definition": 
                "name": "connection.username",
                "type": "STRING",
                "required": false,
                "default_value": null,
                "importance": "MEDIUM",
                "documentation": "The username used to authenticate with Elasticsearch. The default is the null, and authentication will only be performed if  both the username and password are non-null.",
                "group": "Connector",
                "width": "SHORT",
                "display_name": "Connection Username",
                "dependents": [],
                "order": 2
            ,
            "value": 
                "name": "connection.username",
                "value": "elastic",
                "recommended_values": [],
                "errors": [
                    "Could not authenticate the user. Check the 'connection.username' and 'connection.password'. Error message: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target"
                ],
                "visible": true
            
        ,
        
            "definition": 
                "name": "connection.password",
                "type": "PASSWORD",
                "required": false,
                "default_value": null,
                "importance": "MEDIUM",
                "documentation": "The password used to authenticate with Elasticsearch. The default is the null, and authentication will only be performed if  both the username and password are non-null.",
                "group": "Connector",
                "width": "SHORT",
                "display_name": "Connection Password",
                "dependents": [],
                "order": 3
            ,
            "value": 
                "name": "connection.password",
                "value": "[hidden]",
                "recommended_values": [],
                "errors": [
                    "Could not authenticate the user. Check the 'connection.username' and 'connection.password'. Error message: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target"
                ],
                "visible": true
            
        ,
        // ...
    ]

可以在here找到包含所有字段的完整验证响应,其中包含可以使用配置字段的所有信息。

更新 1(2021 年 12 月 8 日):

我发现this document 有更多关于 SSL 的配置

"elastic.security.protocol": "SSL"
"elastic.https.ssl.keystore.location": "/path/to/keystore.jks"
"elastic.https.ssl.keystore.password": "xxx"
"elastic.https.ssl.key.password": "xxx"
"elastic.https.ssl.keystore.type": "JKS"
"elastic.https.ssl.truststore.location": "/path/to/truststore.jks"
"elastic.https.ssl.truststore.password": "xxx"
"elastic.https.ssl.truststore.type": "JKS"
"elastic.https.ssl.protocol": "TLS"

就我而言,我只需要提供者用户名和密码即可成功。但是在上面的配置中,没有地方提供用户名。所以我不确定如何真正正确地编写它。

更新 2(2021 年 12 月 9 日):

我正在运行这些 pod

> kubectl get pods --namespace=elastic
NAME                                 READY   STATUS    RESTARTS   AGE
hm-kibana-kb-77d4d9b456-m6th9        1/1     Running   0          6d3h
hm-elasticsearch-es-default-0        1/1     Running   0          35h

还有这些秘密

kubectl get secrets --namespace=elastic
NAME                                             TYPE                                  DATA   AGE
hm-kibana-kibana-user                            Opaque                                1      6d3h
elastic-hm-kibana-kibana-user                    Opaque                                3      6d3h
hm-kibana-kb-http-ca-internal                    Opaque                                2      6d3h
hm-elasticsearch-es-http-ca-internal             Opaque                                2      6d3h
hm-elasticsearch-es-http-certs-internal          Opaque                                3      6d3h
hm-elasticsearch-es-http-certs-public            Opaque                                2      6d3h
hm-kibana-kb-es-ca                               Opaque                                2      6d3h
hm-kibana-kb-http-certs-internal                 Opaque                                3      6d3h
hm-kibana-kb-http-certs-public                   Opaque                                2      6d3h
hm-elasticsearch-es-transport-ca-internal        Opaque                                2      6d3h
hm-elasticsearch-es-transport-certs-public       Opaque                                1      6d3h
hm-elasticsearch-es-remote-ca                    Opaque                                1      6d3h
hm-elasticsearch-es-elastic-user                 Opaque                                1      6d3h
hm-elasticsearch-es-internal-users               Opaque                                3      6d3h
hm-elasticsearch-es-xpack-file-realm             Opaque                                3      6d3h
hm-elasticsearch-es-default-es-config            Opaque                                1      6d3h
hm-elasticsearch-es-default-es-transport-certs   Opaque                                3      6d3h
hm-kibana-kb-config                              Opaque                                2      6d3h

我可以在本地保存ca.crttls.crttls.key

kubectl get secret hm-elasticsearch-es-http-certs-public \
  --namespace=elastic \
  --output=go-template='index .data "ca.crt" | base64decode ' \
  > ca.crt

kubectl get secret hm-elasticsearch-es-http-certs-public \
  --namespace=elastic \
  --output=go-template='index .data "tls.crt" | base64decode ' \
  > tls.crt

kubectl get secret hm-elasticsearch-es-http-certs-internal \
  --namespace=elastic \
  --output=go-template='index .data "tls.key" | base64decode ' \
  > tls.key

在我必须使用-k 标志禁用证书验证以让curl 成功之前。现在在 Kubernetes 中,我可以在没有 flag 的情况下成功:

curl --request GET \
     --url https://hm-elasticsearch-es-http.elastic:9200 \
     --cacert ca.crt \
     --key tls.key \
     --cert tls.crt \
     --header 'Content-Type: application/json' \
     -u "elastic:passw0rd"

另外,我成功通过

生成keystore.jks
openssl pkcs12 -export \
  -in tls.crt \
  -inkey tls.key \
  -CAfile ca.crt \
  -caname root \
  -out keystore.p12 \
  -password pass:SFLzyT8DPkGGjDtn \
  -name hm-elasticsearch-keystore

keytool -importkeystore \
  -srckeystore keystore.p12 \
  -srcstoretype PKCS12 \
  -srcstorepass SFLzyT8DPkGGjDtn \
  -deststorepass MPx57vkACsRWKVap \
  -destkeypass MPx57vkACsRWKVap \
  -destkeystore keystore.jks \
  -alias hm-elasticsearch-keystore

我仍然不确定 UPDATE 1 中的 truststore 是怎样的。但现在我可以填写关于 keystore 的这一部分:

"elastic.https.ssl.keystore.location": "/path/to/keystore.jks"
"elastic.https.ssl.keystore.password": "MPx57vkACsRWKVap"
"elastic.https.ssl.key.password": "MPx57vkACsRWKVap"
"elastic.https.ssl.keystore.type": "JKS"

但是,我的keystore.jks 目前在我本地的笔记本电脑上。我的 Elasticsearch 和 ElasticsearchSinkConnector 在 Kubernetes 中运行。

"elastic.https.ssl.keystore.location": "/path/to/keystore.jks" 指的是哪里?

【问题讨论】:

elastic.co/guide/en/cloud-on-k8s/current/… 谢谢@OneCricketeer 我已经检查了链接。这是为了提供自己的证书。但是,即使我有自己的ca.crttls.crttls.key,我仍然不确定如何在配置中填写这些字段.. 1) 您需要将这些文件转换为 JKS 文件 2) 否则,在 Connect 之外,ES-API 是否仅使用用户名和密码?例如使用curl -u? @OneCricketeer 1) 我会尝试找到一个如何转换的好教程。 2) 是的,它只适用于我的问题中的curl -u "elastic:passw0rd" -k " https://hm-elasticsearch-es-http.elastic:9200" 之类的用户名和密码。 抱歉,错过了。我假设 curl 调用来自连接容器?我能想到的唯一其他想法是,由于 Connect 使用基于 JVM 的 HTTP 客户端,因此可能需要这些证书,因此您需要添加所有这些 SSL 属性和 HTTPS 用户+密码 【参考方案1】:

首先添加更多背景。我部署Kafka的方式是使用Strimzi:

kubectl create namespace kafka
kubectl apply --filename="https://strimzi.io/install/latest?namespace=kafka" --namespace=kafka
kubectl apply --filename=https://strimzi.io/examples/latest/kafka/kafka-persistent-single.yaml --namespace=kafka

按照问题中的 UPDATE 2,一旦获得 keystore.jks,我通过

创建了秘密
kubectl create secret generic hm-elasticsearch-keystore \
  --from-file=keystore.jks \
  --namespace=kafka

我有文件

kafkaconnect.yaml

apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaConnect
metadata:
  name: hm-connect-cluster
  namespace: kafka
  annotations:
    # use-connector-resources configures this KafkaConnect
    # to use KafkaConnector resources to avoid
    # needing to call the Connect REST API directly
    strimzi.io/use-connector-resources: "true"
spec:
  image: hongbomiao/hm-connect-debezium:latest
  replicas: 1
  bootstrapServers: my-cluster-kafka-bootstrap:9093
  tls:
    trustedCertificates:
      - secretName: my-cluster-cluster-ca-cert
        certificate: ca.crt
  config:
    config.storage.replication.factor: 1
    offset.storage.replication.factor: 1
    status.storage.replication.factor: 1
    config.providers: file
    config.providers.file.class: org.apache.kafka.common.config.provider.FileConfigProvider
  externalConfiguration:
    volumes:
      - name: hm-elasticsearch-keystore-volume
        secret:
          secretName: hm-elasticsearch-keystore

elasticsearch-sink-kafkaconnector.yaml

apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaConnector
metadata:
  name: elasticsearch-sink-connector
  namespace: kafka
  labels:
    strimzi.io/cluster: hm-connect-cluster
spec:
  class: io.confluent.connect.elasticsearch.ElasticsearchSinkConnector
  tasksMax: 1
  # https://docs.confluent.io/kafka-connect-elasticsearch/current/configuration_options.html
  config:
    connector.class: "io.confluent.connect.elasticsearch.ElasticsearchSinkConnector"
    tasks.max: "1"
    topics: "opa_db_server.public.roles"
    connection.url: "https://hm-elasticsearch-es-http.elastic:9200"
    connection.username: "elastic"
    connection.password: "passw0rd"
    transforms: "unwrap,key"
    transforms.unwrap.type: "io.debezium.transforms.ExtractNewRecordState"
    transforms.unwrap.drop.tombstones: "false"
    transforms.key.type: "org.apache.kafka.connect.transforms.ExtractField$Key"
    transforms.key.field: "role_id"
    key.ignore: "false"
    behavior.on.null.values: "delete"
    elastic.security.protocol: "SSL"
    elastic.https.ssl.keystore.location: "/opt/kafka/external-configuration/hm-elasticsearch-volume/keystore.jks"
    elastic.https.ssl.keystore.password: "MPx57vkACsRWKVap"
    elastic.https.ssl.key.password: "MPx57vkACsRWKVap"
    elastic.https.ssl.keystore.type: "JKS"
    elastic.https.ssl.truststore.location: "/opt/kafka/external-configuration/hm-elasticsearch-keystore-volume/keystore.jks"
    elastic.https.ssl.truststore.password: "MPx57vkACsRWKVap"
    elastic.https.ssl.truststore.type: "JKS"
    elastic.https.ssl.protocol: "TLS1.3"

注意 keystore 和 truststore 共享同一个。

然后只需要运行

kubectl apply --filename=kafkaconnect.yaml
kubectl apply --filename=elasticsearch-sink-kafkaconnector.yaml

现在可以了!

【讨论】:

以上是关于如何在 Kafka 连接器中正确连接 Elastic Operator 部署的 Elasticsearch?的主要内容,如果未能解决你的问题,请参考以下文章

使用 Kafka Connect Elasticsearch 连接器的消息顺序

如何在 Strimzi 中使用 Kafka 连接

如何开始在开源 Apache Kafka 中运行 kafka 连接器?

kafka jdbc sink连接器抛出org.apache.kafka.connect.errors.DataException(结构模式的字段名称未正确指定)插入PG表

在Kafka Connect中,如何连接多个kafka集群?

flink sql client 连接kafka解析avro数据 (avro ArrayIndexOutOfBoundsException 解决办法)