feat: docker-compose kafka 설정 추가#1
Conversation
There was a problem hiding this comment.
Pull request overview
프로덕션용 docker-compose에서 Kafka의 advertised.listeners를 고정 호스트/포트 값 대신 환경변수 기반으로 설정 가능하게 변경합니다.
Changes:
- Kafka
KAFKA_ADVERTISED_LISTENERS를${KAFKA_EXTERNAL_HOST}/${KAFKA_EXTERNAL_PORT}환경변수 기반으로 변경 - (기능 변화 없이) 네트워크 드라이버 라인 포맷만 변경
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| KAFKA_CONTROLLER_QUORUM_VOTERS: '1@kafka:9103' | ||
| KAFKA_LISTENERS: 'INTERNAL://0.0.0.0:29092,EXTERNAL://0.0.0.0:9102,CONTROLLER://0.0.0.0:9103' | ||
| KAFKA_ADVERTISED_LISTENERS: 'INTERNAL://kafka:29092,EXTERNAL://devnogi.ddns.net:9102' | ||
| KAFKA_ADVERTISED_LISTENERS: "INTERNAL://kafka:29092,EXTERNAL://${KAFKA_EXTERNAL_HOST}:${KAFKA_EXTERNAL_PORT}" |
There was a problem hiding this comment.
KAFKA_ADVERTISED_LISTENERS now depends on ${KAFKA_EXTERNAL_HOST} / ${KAFKA_EXTERNAL_PORT}, but this compose file doesn’t provide defaults and the port mapping is still hard-coded to 9102:9102. If those env vars are unset (or KAFKA_EXTERNAL_PORT differs from 9102), Kafka will advertise an invalid/unreachable address and clients will fail to connect. Consider enforcing required values via ${VAR:?message} and/or wiring the ports: mapping to the same ${KAFKA_EXTERNAL_PORT} (with a sane default like :-9102) so the advertised port cannot drift from the exposed port.
|
CLUSTER_ID: 아래에 이코드 추가해주세요. KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1 |
No description provided.