p53
p53
when you plan to implement this?
@afoley-st don't you miss ```--sasl-enable ``` option?
@afoley-st no ```--proxy-listener-tls-enable``` should not be requirement. What version of client/server you have? What is your ```listener.security.protocol.map```
and client kafka version?
@afoley-st did you try also with 2.3 see https://github.com/grepplabs/kafka-proxy/issues/28#issuecomment-582160739
@afoley-st you should connect to your kafka-proxy server without SASL credentials/SSL (if are doing it right now, kafka-proxy already authenticates/encrypts connection with confluent kafka) as @datafisk mentioned
i have same problem, here are details ## Report Thank you for trying **conjure-up**! Before reporting a bug please make sure you've gone through this checklist: - [no] Is this...
and here are sosreport and conjure-up logs [conjure-up.tar.gz](https://github.com/conjure-up/conjure-up/files/1665953/conjure-up.tar.gz) [sosreport.tar.gz](https://github.com/conjure-up/conjure-up/files/1665961/sosreport.tar.gz)
@FillZpp [v0.25.2](https://github.com/kubernetes/client-go/tree/v0.25.2) should contain remove method
``` /usr/local/bin/kafkacat -V kafkacat - Apache Kafka producer and consumer tool https://github.com/edenhill/kafkacat Copyright (c) 2014-2019, Magnus Edenhill Version 1.6.0 (JSON, Avro, Transactions, librdkafka 1.5.0 builtin.features=gzip,snappy,ssl,sasl,regex,lz4,sasl_gssapi,sasl_plain,sasl_scram,plugins,zstd,sasl_oauthbearer) ```