[ 
https://issues.apache.org/jira/browse/KAFKA-10737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ning Zhang updated KAFKA-10737:
-------------------------------
    Description: 
As MM2 is adopted by more users, new and advanced use cases requires Kafka 
clusters to be secure, and one way to make this happen is SSL-enabled cluster.

Currently there is no clear doc on how to configure MM2 so that it can consume 
from or produce to a SSL-enable cluster. Some users spent quite amount of time 
and found out the right config (see 
https://issues.apache.org/jira/browse/KAFKA-10704). So it would be great to 
clearly doc on this.

  was:
As MM2 is adopted by more users, new and advanced use cases requires Kafka 
clusters to be secure, and one way to make this happen is SSL-enabled cluster.

Currently there is no clear doc on how to configure MM2 so that it can consume 
from or produce to a SSL-enable cluster. Some users spent quite amount of time 
and found out the right config (see ). So it would be great to clearly doc on 
this.


> MirrorMaker 2: clarify how to produce to or consume from SSL-enabled cluster 
> in README.md 
> ------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-10737
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10737
>             Project: Kafka
>          Issue Type: Improvement
>          Components: mirrormaker
>    Affects Versions: 2.7.0
>            Reporter: Ning Zhang
>            Assignee: Ning Zhang
>            Priority: Minor
>
> As MM2 is adopted by more users, new and advanced use cases requires Kafka 
> clusters to be secure, and one way to make this happen is SSL-enabled cluster.
> Currently there is no clear doc on how to configure MM2 so that it can 
> consume from or produce to a SSL-enable cluster. Some users spent quite 
> amount of time and found out the right config (see 
> https://issues.apache.org/jira/browse/KAFKA-10704). So it would be great to 
> clearly doc on this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to