Strimzi
Kafka MirrorMaker2 cannot connect to kafka node with TLS. Returns a timeout error #10852
-
|
I have two k8s setups on which kafka clusters are running. On my origin setup no TLS or authentication is required. My target setup has both SCRAM-SHA-512 and TLS setup. spec:
clusters:
- alias: source-dummy-six
bootstrapServers: origin-kafka:9092
- alias: target-dummy-six
authentication:
passwordSecret:
password: target-password
secretName: password-secret-dummy-six
type: scram-sha-512
username: kafka-username
bootstrapServers: 10.11.12.13:32182
config:
config.storage.replication.factor: -1
config.storage.topic: dummy-six-configs
group.id: dummy-six-group-id
offset.storage.replication.factor: -1
offset.storage.topic: dummy-six-offset
reconnect.backoff.max.ms: 2000
reconnect.backoff.ms: 2000
request.timeout.ms: 60000
retry.backoff.max.ms: 2000
retry.backoff.ms: 2000
socket.connection.setup.timeout.ms: 30000
ssl.endpoint.identification.algorithm: ""
status.storage.replication.factor: -1
status.storage.topic: dummy-six-status
tls:
trustedCertificates:
- certificate: ca.cert
secretName: target-tls-secret-dummy-six
connectCluster: target-dummy-six
logging:
loggers:
connect.root.logger.level: INFO
type: inline
metricsConfig:
type: jmxPrometheusExporter
valueFrom:
configMapKeyRef:
key: mirrormaker-metrics-config
name: mirror-maker-2-metrics
mirrors:
- checkpointConnector:
config:
checkpoints.topic.replication.factor: 1
offset-syncs.topic.location: target
refresh.groups.interval.seconds: 20
replication.policy.class: com.company.CustomRepPolicy
replication.policy.dest.metric.topic.name: test_metric_con
sync.group.offsets.enabled: false
groupsPattern: .*
heartbeatConnector:
config:
heartbeats.topic.replication.factor: 1
sourceCluster: source-dummy-six
sourceConnector:
config:
offset-syncs.topic.location: target
offset-syncs.topic.replication.factor: 1
refresh.topics.interval.seconds: 20
replication.factor: 1
replication.policy.class: com.company.CustomRepPolicy
replication.policy.dest.metric.topic.name: test_metric_con
replication.policy.separator: .
sync.group.offsets.enabled: false
sync.topic.acls.enabled: "true"
topic.creation.default.message.format.version: 2.8-IV0
topic.creation.default.partitions: -1
topic.creation.default.replication.factor: -1
tasksMax: 4
targetCluster: target-dummy-six
topicsPattern: my_target_topicThis is the error I get What I notice is I am providing the target bootstrap-server as Furthermore when I try to check the connection on But when I do the same with I have also verified the tls certificate by executing this command and cross checking the ca-cert I have provided with the last certificate of the output of this command Also on my target cluster I have not defined any acls. So by default all permissions should be enabled. As determined by the output of this (I have changed the actual IP addresses) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
The Mirror Maker 2 config seems to be fine in theory. So I think you need to be looking at whether your security configuration is really correct, whether the networking is working etc. But those depend on your environment, so nobody can really help you with those. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, it turned out to be a network issue. The hostname the bootstrap server was resolving to |
Beta Was this translation helpful? Give feedback.
The Mirror Maker 2 config seems to be fine in theory. So I think you need to be looking at whether your security configuration is really correct, whether the networking is working etc. But those depend on your environment, so nobody can really help you with those.