fix redpanda and registry
This commit is contained in:
56
redpanda/bootstrap.yml
Normal file
56
redpanda/bootstrap.yml
Normal file
@@ -0,0 +1,56 @@
|
||||
# =================================================================
|
||||
# This file defines initial cluster properties for a Redpanda cluster.
|
||||
# Some of these settings are intended for quickstart development and evaluation
|
||||
# and are not suitable for production environments.
|
||||
#
|
||||
# For more information on bootstrap files, see:
|
||||
# https://docs.redpanda.com/current/deploy/deployment-option/self-hosted/manual/production/production-deployment/#configure-a-bootstrap-file
|
||||
# =================================================================
|
||||
|
||||
#
|
||||
# Enable SASL authentication for the Kafka and Admin APIs.
|
||||
# https://docs.redpanda.com/current/reference/properties/cluster-properties/#admin_api_require_auth
|
||||
admin_api_require_auth: true
|
||||
# At least one superuser is required to be able to create other SASL users
|
||||
# https://docs.redpanda.com/current/reference/properties/cluster-properties/#superusers
|
||||
superusers:
|
||||
- im-admin
|
||||
# https://docs.redpanda.com/current/reference/properties/cluster-properties/#enable_sasl
|
||||
enable_sasl: true
|
||||
# Allow topics to be created on first access.
|
||||
# https://docs.redpanda.com/current/reference/properties/cluster-properties/#auto_create_topics_enabled
|
||||
auto_create_topics_enabled: true
|
||||
# Enable data transforms.
|
||||
# https://docs.redpanda.com/current/develop/data-transforms/how-transforms-work/
|
||||
#data_transforms_enabled: true
|
||||
# Enable audit logging (enterprise feature).
|
||||
# https://docs.redpanda.com/current/manage/audit-logging/
|
||||
#audit_enabled: true
|
||||
# Enable Tiered Storage (enterprise feature).
|
||||
# https://docs.redpanda.com/current/manage/tiered-storage/
|
||||
#cloud_storage_enabled: true
|
||||
#cloud_storage_region: local
|
||||
#cloud_storage_access_key: minio
|
||||
#cloud_storage_secret_key: redpandaTieredStorage7
|
||||
#cloud_storage_api_endpoint: minio
|
||||
#cloud_storage_api_endpoint_port: 9000
|
||||
#cloud_storage_disable_tls: true
|
||||
#cloud_storage_bucket: redpanda
|
||||
# Forces segments to be uploaded to Tiered Storage faster for the purposes of the quickstart
|
||||
# https://docs.redpanda.com/current/reference/properties/object-storage-properties/#cloud_storage_segment_max_upload_interval_sec
|
||||
#cloud_storage_segment_max_upload_interval_sec: 60
|
||||
# Continuous Data Balancing (enterprise feature) continuously monitors your node and rack availability and disk usage. This enables self-healing clusters that dynamically balance partitions, ensuring smooth operations and optimal cluster performance.
|
||||
# https://docs.redpanda.com/current/manage/cluster-maintenance/continuous-data-balancing/
|
||||
#partition_autobalancing_mode: continuous
|
||||
# Enable Redpanda to collect consumer group metrics.
|
||||
# https://docs.redpanda.com/current/reference/properties/cluster-properties/#enable_consumer_group_metrics
|
||||
enable_consumer_group_metrics:
|
||||
- "group"
|
||||
- "partition"
|
||||
- "consumer_lag"
|
||||
# Lower the interval for the quickstart
|
||||
# https://docs.redpanda.com/current/reference/properties/cluster-properties/#consumer_group_lag_collection_interval_sec
|
||||
consumer_group_lag_collection_interval_sec: 60
|
||||
# Enable Redpanda to collect host metrics.
|
||||
# https://docs.redpanda.com/current/reference/properties/cluster-properties/#enable_host_metrics
|
||||
enable_host_metrics: true
|
||||
@@ -1,62 +0,0 @@
|
||||
name: redpanda-quickstart-one-broker
|
||||
networks:
|
||||
redpanda_network:
|
||||
driver: bridge
|
||||
services:
|
||||
redpanda-0:
|
||||
command:
|
||||
- redpanda
|
||||
- start
|
||||
- --kafka-addr internal://0.0.0.0:9092,external://0.0.0.0:19092
|
||||
# Address the broker advertises to clients that connect to the Kafka API.
|
||||
# Use the internal addresses to connect to the Redpanda brokers'
|
||||
# from inside the same Docker network.
|
||||
# Use the external addresses to connect to the Redpanda brokers'
|
||||
# from outside the Docker network.
|
||||
- --advertise-kafka-addr internal://redpanda-0:9092,external://localhost:19092
|
||||
- --pandaproxy-addr internal://0.0.0.0:8082,external://0.0.0.0:18082
|
||||
# Address the broker advertises to clients that connect to the HTTP Proxy.
|
||||
- --advertise-pandaproxy-addr internal://redpanda-0:8082,external://localhost:18082
|
||||
- --schema-registry-addr internal://0.0.0.0:8081,external://0.0.0.0:18081
|
||||
# Redpanda brokers use the RPC API to communicate with each other internally.
|
||||
- --rpc-addr redpanda-0:33145
|
||||
- --advertise-rpc-addr redpanda-0:33145
|
||||
# Mode dev-container uses well-known configuration properties for development in containers.
|
||||
- --mode dev-container
|
||||
# Tells Seastar (the framework Redpanda uses under the hood) to use 1 core on the system.
|
||||
- --smp 1
|
||||
- --default-log-level=info
|
||||
image: docker.redpanda.com/redpandadata/redpanda:v25.2.9
|
||||
container_name: redpanda-0
|
||||
volumes:
|
||||
- ./redpanda-0:/var/lib/redpanda/data
|
||||
networks:
|
||||
- redpanda_network
|
||||
ports:
|
||||
- 18081:18081
|
||||
- 18082:18082
|
||||
- 19092:19092
|
||||
- 19644:9644
|
||||
console:
|
||||
container_name: redpanda-console
|
||||
image: docker.redpanda.com/redpandadata/console:v3.2.2
|
||||
networks:
|
||||
- redpanda_network
|
||||
entrypoint: /bin/sh
|
||||
command: -c 'echo "$$CONSOLE_CONFIG_FILE" > /tmp/config.yml; /app/console'
|
||||
environment:
|
||||
CONFIG_FILEPATH: /tmp/config.yml
|
||||
CONSOLE_CONFIG_FILE: |
|
||||
kafka:
|
||||
brokers: ["redpanda-0:9092"]
|
||||
schemaRegistry:
|
||||
enabled: true
|
||||
urls: ["http://redpanda-0:8081"]
|
||||
redpanda:
|
||||
adminApi:
|
||||
enabled: true
|
||||
urls: ["http://redpanda-0:9644"]
|
||||
ports:
|
||||
- 8086:8080
|
||||
depends_on:
|
||||
- redpanda-0
|
||||
Reference in New Issue
Block a user