c++ 版 Kafka 服务 Redpanda

项目地址：https://github.com/redpanda-data/redpanda docker 镜像：docker pull redpandadata/redpanda:v24.2.7 ⚠️ docker 镜像貌似在国内不能用了，使用阿里云加速也没用

官方文档：https://docs.redpanda.com/current/deploy/deployment-option/self-hosted/docker-image/

docker 环境变量说明

• CONNECT_BOOTSTRAP_SERVERS Comma-separated list of host and port pairs that are the addresses of the Redpanda brokers.

• CONNECT_CONFIGURATION Properties-based Kafka Connect configuration.

• CONNECT_ADDITIONAL_CONFIGURATION Comma-separated Kafka Connect properties. This can be used as an alternative to the CONNECT_CONFIGURATION property. If the same Kafka Connect property is defined in CONNECT_CONFIGURATION and CONNECT_ADDITIONAL_CONFIGURATION, the one from CONNECT_ADDITIONAL_CONFIGURATION is used. Example: offset.flush.interval.ms=1000,producer.linger.ms=1

• CONNECT_SASL_MECHANISM SASL mechanism. Allowed values: "plain","scram-sha-256", or "scram-sha-512". Do not set if SASL is not used. Default: not set

• CONNECT_SASL_USERNAME SASL username used to authenticate connecting to a Redpanda broker. Default: not set

• CONNECT_SASL_PASSWORD_FILE Relative path to a file containing the SASL password, relative to the /opt/kafka/connect-password directory. If the file is in /opt/kafka/connect-password/pass-dir/password, then set pass-dir/password. The SASL password is given in plain text. Default: not set

• CONNECT_TLS_ENABLED Set to "true" if TLS enabled, and "false" if not. Default: "false"

• CONNECT_TLS_AUTH_CERT TLS authentication certificate location (relative path from /opt/kafka/connect-certs/). For example: "user-secret/user.crt" when file is in /opt/kafka/connect-certs/user-secret/user.crt

• CONNECT_TLS_AUTH_KEY TLS authentication key location (relative path from /opt/kafka/connect-certs/). For example: "user-secret/user.key" when file is in /opt/kafka/connect-certs/user-secret/user.key

• CONNECT_TRUSTED_CERTS Truststore locations (relative path from /opt/kafka/connect-certs/). For example: "my-secret/ca.crt;my-secret/new-cert.crt" when file is in /opt/kafka/connect-certs/my-secret/ca.crt and /opt/kafka/connect-certs/my-secret/new-cert.crt

• CONNECT_ADDITIONAL_TLS_AUTH_CERT Additional TLS authentication certificate location, used, for example, to connect with the source MM2 cluster, (relative path from /opt/kafka/connect-certs/). For example: "user-secret/user.crt" when file is in /opt/kafka/connect-certs/user-secret/user.crt

• CONNECT_ADDITIONAL_TLS_AUTH_KEY Additional TLS authentication key location, used, for example, to connect with the source MM2 cluster (relative path from /opt/kafka/connect-certs/). For example: "user-secret/user.key" when file is in /opt/kafka/connect-certs/user-secret/user.key

• CONNECT_ADDITIONAL_TRUSTED_CERTS Additional truststore locations, used, for example, to connect with the source MM2 cluster (relative path from /opt/kafka/connect-certs/). For example: "my-secret/cert.crt;my-secret/new-cert.crt" when file is in /opt/kafka/connect-certs/my-secret/cert.crt and /opt/kafka/connect-certs/my-secret/new-cert.crt

• CONNECT_METRICS_ENABLED Set to "true to enable Prometheus metrics, port 9404. Set to "false" to disable. Default: "true"

• CONNECT_PLUGIN_PATH Comma-separated list of directories with plugins to load by Kafka Connect. Default: /opt/kafka/redpanda-plugins

• CONNECT_GC_LOG_ENABLED Set to "true" to enable GC logging. Set to "false" to disable GC logs. Default: "false"

• CONNECT_HEAP_OPTS JVM heap options. For example -Xms2G -Xmx2G. Default: -Xms256M -Xmx256M

• CONNECT_LOG4J_CONFIGURATION By default, Kafka Connect logs at "info" info level using Console appender. Use this property to pass custom log4j properties-based configuration.

• CONNECT_LOG_LEVEL By default, Kafka Connect logs at "warn" info level using Console appender. Use "info" to change the log level to info or "debug" for debug log level.