### Download and Start Redpanda Self-Managed (Bash) Source: https://docs.redpanda.com/current/get-started/quick-start This bash script downloads the Redpanda quickstart archive, extracts it, and starts the Redpanda services using Docker Compose. It assumes you have Docker and curl installed. ```bash mkdir redpanda-quickstart && cd redpanda-quickstart && \ curl -sSL https://docs.redpanda.com/redpanda-quickstart.tar.gz | tar xzf - && \ cd docker-compose && docker compose up -d ``` -------------------------------- ### Download and Start Redpanda Self-Managed with Docker Compose Source: https://docs.redpanda.com/25.1/get-started/quick-start This script downloads a Redpanda quickstart archive, extracts it, and starts the Redpanda services using Docker Compose. It assumes Docker is installed and accessible. ```bash mkdir redpanda-quickstart && cd redpanda-quickstart && \ curl -sSL https://docs.redpanda.com/25.1-redpanda-quickstart.tar.gz | tar xzf - && \ cd docker-compose && docker compose up -d ``` -------------------------------- ### Produce to a topic using rpk Source: https://docs.redpanda.com/api/doc/cloud-dataplane/topic/topic-quickstart This example demonstrates how to produce a message to a topic using the `rpk` command-line tool. It requires the `rpk` tool to be installed and configured. ```bash echo "hello world" | rpk topic produce test-topic ``` -------------------------------- ### Download and Start Redpanda Self-Managed (Bash) Source: https://docs.redpanda.com/24.3/get-started/quick-start This bash script downloads, extracts, and starts a Redpanda self-managed cluster using Docker Compose. It creates a directory, fetches a compressed archive from a URL, extracts it, and then uses Docker Compose to bring up the services defined in the `docker-compose.yml` file. Ensure Docker and curl are installed. ```bash mkdir redpanda-quickstart && cd redpanda-quickstart && \ curl -sSL https://docs.redpanda.com/24.3-redpanda-quickstart.tar.gz | tar xzf - && \ cd docker-compose && docker compose up -d ``` -------------------------------- ### Example: Start a Three-Broker Redpanda Cluster Source: https://docs.redpanda.com/24.1/reference/rpk/rpk-container/rpk-container-start Demonstrates starting a Redpanda cluster with three brokers. This is useful for testing multi-node configurations locally. ```bash rpk container start -n 3 ``` -------------------------------- ### Install rpk on macOS using Homebrew Source: https://docs.redpanda.com/23.3/get-started/quick-start Guide to installing the `rpk` command-line tool on macOS via Homebrew. This method installs the latest version, which is recommended for use with the latest Redpanda version. It includes steps for installing Homebrew if not already present. ```bash brew install redpanda-data/tap/redpanda ``` ```bash rpk version ``` -------------------------------- ### Install `rpk` FIPS Compliance on Debian/Ubuntu Source: https://docs.redpanda.com/redpanda-connect/get-started/quickstarts/rpk Installs Redpanda `rpk` and `redpanda-connect` packages for FIPS compliance on Debian/Ubuntu systems. This involves upgrading the distribution, adding the Redpanda repository, and then installing the FIPS-compliant packages. ```bash sudo apt upgrade ``` ```bash curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' | sudo -E bash ``` ```bash sudo apt install -y redpanda-rpk-fips redpanda-connect-fips ``` ```bash rpk connect --version ``` ```bash sudo apt update ``` -------------------------------- ### Install `rpk` FIPS Compliance on RHEL Source: https://docs.redpanda.com/redpanda-connect/get-started/quickstarts/rpk Installs Redpanda `rpk` and `redpanda-connect` packages for FIPS compliance on RHEL systems. This involves upgrading the distribution, adding the Redpanda repository, and then installing the FIPS-compliant packages. ```bash sudo dnf upgrade ``` ```bash curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.rpm.sh' | sudo -E bash ``` ```bash sudo dnf install -y redpanda-rpk-fips redpanda-connect-fips ``` ```bash rpk connect --version ``` ```bash sudo dnf update ``` -------------------------------- ### Initiate a prompt with search-bluesky-posts tool Source: https://docs.redpanda.com/redpanda-connect/ai-agents/mcp-server/quickstart Starts a conversation with Claude Code by entering a natural language prompt that utilizes the 'search-bluesky-posts' tool. This example searches for the latest news about Redpanda Data. ```bash claude Search Bluesky for the latest news about Redpanda Data ``` -------------------------------- ### Run Advanced Pipeline with Sample JSON Data Source: https://docs.redpanda.com/redpanda-connect/get-started/quickstarts/rpk Tests the advanced Redpanda Connect pipeline by piping sample JSON data to it via standard input. This example shows how to send multiple JSON documents and observe the transformed output. ```bash echo '{"id":"1","names":["celine","dion"]} {"id":"2","names":["chad","robert","kroeger"]}' | rpk connect run connect.yaml ``` ```bash echo '{"id":"1","names":["celine","dion"]} {"id":"2","names":["chad","robert","kroeger"]}' | docker run --rm -i -v $(pwd)/connect.yaml:/connect.yaml docker.redpanda.com/redpandadata/connect run ``` -------------------------------- ### Start MCP Server Source: https://docs.redpanda.com/redpanda-connect/ai-agents/mcp-server/quickstart Command to start the Redpanda Connect MCP server, exposing the defined tools with a specified tag. ```APIDOC ## Start the MCP Server ### Command ```bash rpk connect mcp-server --address localhost:4195 --tag example ``` ### Description This command initiates the MCP server on `localhost:4195`. Only tools tagged with `example` (or the tag specified with `--tag`) will be exposed and made discoverable by AI agents. This tagging mechanism helps in isolating experiments and controlling which tools are made available. ### Parameters #### Command Line Arguments - **--address** (string) - Optional - The address and port for the MCP server to listen on. Defaults to `localhost:4195`. - **--tag** (string) - Optional - A tag to filter which tools are exposed. Only tools with this tag will be discoverable. ### Expected Output Example ``` time=2025-06-27T15:20:27.976+01:00 level=INFO msg="Registering processor tool" label=search-bluesky-posts time=2025-06-27T15:20:27.978+01:00 level=INFO msg="Successfully loaded Redpanda license" expires_at=2035-06-25T15:20:27+01:00 license_org="" license_type="open source" ``` ``` -------------------------------- ### Run Redpanda Connect Pipeline Source: https://docs.redpanda.com/redpanda-connect/get-started/quickstarts/rpk Executes a Redpanda Connect pipeline using a specified configuration file. This command is used to test and run the defined stream processing logic. Docker installations require mounting the config file as a volume. ```bash rpk connect run connect.yaml ``` ```bash docker run --rm -it -v $(pwd)/connect.yaml:/connect.yaml docker.redpanda.com/redpandadata/connect run ``` -------------------------------- ### rpk connect install Source: https://docs.redpanda.com/24.2/reference/rpk/rpk-connect/rpk-connect-install Installs Redpanda Connect. By default, it installs the latest version. You can specify a version using --connect-version or force installation with --force. ```APIDOC ## POST /rpk/connect/install ### Description Installs Redpanda Connect. This command can install the latest version or a specific version using the `--connect-version` flag. Use the `--force` flag to override existing installations. ### Method POST ### Endpoint /rpk/connect/install ### Parameters #### Query Parameters - **connect-version** (string) - Optional - The Redpanda Connect version to install. Defaults to 'latest'. - **force** (-) - Optional - Force the installation of Redpanda Connect. - **config** (string) - Optional - Path to the Redpanda or `rpk` config file. Defaults to standard search paths. - **config-opt** (stringArray) - Optional - Override `rpk` configuration settings. - **profile** (string) - Optional - Profile to use for `rpk` commands. - **verbose** (-) - Optional - Enable verbose logging. ### Request Example ```json { "connect-version": "4.32.0", "force": true } ``` ### Response #### Success Response (200) - **message** (string) - Confirmation message of the installation. #### Response Example ```json { "message": "Redpanda Connect installed successfully." } ``` ``` -------------------------------- ### Help Link Example Source: https://docs.redpanda.com/api/doc/cloud-dataplane/group/endpoint-redpanda-connect-pipelines Shows an example of the Help object, which provides URLs for additional information or actions to resolve an error. This is useful for guiding users on how to fix issues, such as enabling a service. ```json { "description": "Enable the Pub/Sub API in the Google Cloud Console.", "url": "https://console.cloud.google.com/apis/library/pubsub.googleapis.com?project=example-project" } ``` -------------------------------- ### Install Redpanda on Debian/Ubuntu Source: https://docs.redpanda.com/25.1/deploy/deployment-option/self-hosted/manual/production/production-deployment Installs the Redpanda application and its core dependencies on Debian or Ubuntu systems using `apt`. This command downloads and executes a setup script, then installs the 'redpanda' package. ```bash curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' \ | sudo -E bash && sudo apt install redpanda -y ``` -------------------------------- ### Example: Start Redpanda with Random Ports Source: https://docs.redpanda.com/24.1/reference/rpk/rpk-container/rpk-container-start Shows how to start a single-broker Redpanda cluster where all listeners are assigned random available ports. This is convenient for avoiding port conflicts. ```bash rpk container start --any-port ``` -------------------------------- ### Install Redpanda on Debian/Ubuntu Source: https://docs.redpanda.com/24.2/deploy/deployment-option/self-hosted/manual/production/dev-deployment Installs the Redpanda application and supporting libraries on Debian/Ubuntu based systems using apt. This command first fetches and executes a setup script, then installs the 'redpanda' package. ```bash curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' | sudo -E bash && sudo apt install redpanda -y ``` -------------------------------- ### Example: Start Redpanda with Custom Admin Ports Source: https://docs.redpanda.com/24.1/reference/rpk/rpk-container/rpk-container-start Demonstrates starting a three-broker Redpanda cluster while specifying the Admin API port for each individual broker. This allows fine-grained control over access to the Admin API. ```bash rpk container start --admin-ports 9644,9645,9646 ``` -------------------------------- ### Help Link Example Source: https://docs.redpanda.com/api/doc/cloud-dataplane/operation/operation-pipelineservice_stoppipeline Shows an example of the Help object, which provides URLs for additional information or actions to resolve an error. This is useful for guiding users on how to fix encountered issues. ```json { "description": "Enable the Pub/Sub API for your project.", "url": "https://console.cloud.google.com/apis/enableapi/pubsub.googleapis.com?project=my-project-id" } ``` -------------------------------- ### Example: Start Redpanda with Specific Kafka and Console Ports Source: https://docs.redpanda.com/24.1/reference/rpk/rpk-container/rpk-container-start Illustrates starting a Redpanda cluster and explicitly setting the Kafka and Console listener ports. This is helpful for integrating with other services that expect specific ports. ```bash rpk container start --kafka-ports 9092 --console-port 8080 ``` -------------------------------- ### Get Started with Redpanda Connect using rpk Source: https://docs.redpanda.com/redpanda-connect/get-started/quickstarts This section details how to deploy your first pipelines using Redpanda Connect and the `rpk` command-line tool. It's designed for users who want hands-on experience with local instances. ```text Get Started with Redpanda Connect using `rpk` Deploy your first pipelines using Redpanda Connect and `rpk`. ``` -------------------------------- ### Create a Redpanda topic using rpk Source: https://docs.redpanda.com/24.3/get-started/rpk-quickstart Creates a new topic named 'tutorial' in Redpanda. This is the first step before producing or consuming data. Requires a running Redpanda cluster and the rpk CLI installed. ```bash rpk topic create tutorial ``` -------------------------------- ### Redpanda CLI Quickstart with rpk Commands Source: https://docs.redpanda.com/current/get-started/quickstarts Learn basic Redpanda operations using the `rpk` command-line tool. This includes creating, producing to, describing, and deleting topics, as well as consuming records and managing consumer groups. No external dependencies beyond the Redpanda CLI installation are required. ```bash # Example: Create a topic rpk topic create my-topic # Example: Produce records to a topic rpc topic produce my-topic -f data.txt # Example: Consume records from a topic rpc topic consume my-topic # Example: Describe a topic rpc topic describe my-topic # Example: Delete a topic rpc topic delete my-topic # Example: Manage consumer groups rpc group list rpc group describe my-group ``` -------------------------------- ### Add and Install Redpanda Helm Chart Source: https://docs.redpanda.com/redpanda-connect/get-started/helm-chart Installs the Redpanda Helm chart by adding the repository, updating the cache, and performing the installation in a specified namespace. This is a prerequisite for deploying Redpanda Connect. ```bash helm repo add redpanda https://charts.redpanda.com__ helm repo update__ helm install redpanda-connect redpanda/connect --namespace --create-namespace__ ``` -------------------------------- ### Describe a Redpanda topic using rpk Source: https://docs.redpanda.com/24.3/get-started/rpk-quickstart Retrieves and displays the configuration and status of the 'tutorial' topic. This helps verify the topic's readiness for use. Requires a running Redpanda cluster and the rpk CLI. ```bash rpk topic describe tutorial ``` -------------------------------- ### Example: Checking Redpanda Container Status after QuickStart Source: https://docs.redpanda.com/24.3/reference/rpk/rpk-container/rpk-container-status This example demonstrates how to use `rpk container status` after following the 'QuickStart - Deploy Redpanda to Docker with Three Nodes' guide. It shows the expected output, including node ID, status, and network addresses. ```bash rpk container status NODE-ID STATUS KAFKA-ADDRESS ADMIN-ADDRESS PROXY-ADDRESS SCHEMA-REGISTRY-ADDRESS 0 running 127.0.0.1:9092 127.0.0.1:9644 127.0.0.1:8082 127.0.0.1:8081 Redpanda Console started in: http://localhost:8080 You can use rpk to interact with this cluster. E.g: rpk cluster info rpk cluster health You may also set an environment variable with the comma-separated list of broker addresses: export REDPANDA_BROKERS="127.0.0.1:34189,127.0.0.1:45523,127.0.0.1:37223" rpk cluster info ``` -------------------------------- ### Initialize Redpanda Connect MCP Server Project Source: https://docs.redpanda.com/redpanda-connect/ai-agents/mcp-server/quickstart Creates a new directory and initializes a Redpanda Connect MCP server project. This scaffolds the necessary directories and template YAML files for defining tools and observability resources. ```bash mkdir redpanda-connect-mcp cd redpanda-connect-mcp rpk connect mcp-server init ``` -------------------------------- ### Help Link Example Source: https://docs.redpanda.com/api/doc/cloud-controlplane/operation/operation-serverlessregionservice_listserverlessregions An example of a Help error detail, providing a URL for additional information or actions related to an error. This can guide users on how to resolve the issue, such as enabling a required service. ```json { "@type": "type.googleapis.com/google.rpc.Help", "links": [ { "description": "Enable the Pub/Sub API", "url": "https://console.cloud.google.com/apis/library/pubsub.googleapis.com?project=my-project-id" } ] } ``` -------------------------------- ### Create and consume from a Redpanda topic with a consumer group using rpk Source: https://docs.redpanda.com/24.3/get-started/rpk-quickstart Consumes records from the 'tutorial' topic and organizes the consumer into a group named 'tutorial-group'. The consumer group is created automatically when consumption begins. Requires a running Redpanda cluster and the rpk CLI. ```bash rpk topic consume tutorial --group tutorial-group ``` -------------------------------- ### Example Redpanda Connect Version Output (JSON) Source: https://docs.redpanda.com/redpanda-connect/get-started/helm-chart This is an example JSON output when querying the `/version` endpoint of the Redpanda Connect HTTP server. It provides the version of the Redpanda Connect instance and the build timestamp. ```json { "version": "v4.38.0", "built": "2024-10-17T09:27:42Z" } ``` -------------------------------- ### Redpanda CLI: Basic Topic and Consumer Group Management with rpk Source: https://docs.redpanda.com/24.3/get-started/quickstarts This snippet demonstrates how to use the Redpanda CLI (rpk) for fundamental tasks. It covers creating, producing to, describing, and deleting topics, as well as consuming records and managing consumer groups. No external dependencies are required beyond the Redpanda CLI installation. ```bash # Create a topic rpk topic create my_topic # Produce messages to a topic rpc topic produce my_topic -f messages.txt # Describe a topic rpk topic describe my_topic # Delete a topic rpk topic delete my_topic # Consume messages from a topic rpc topic consume my_topic # Manage consumer groups rpc group list rpc group describe my_group rpc group delete my_group ``` -------------------------------- ### Docker Compose Up Output Source: https://docs.redpanda.com/23.3/get-started/quick-start This output indicates the successful creation and startup of all services defined in the `docker-compose.yml` file. It shows the network, volumes, and containers (Redpanda instances and Console) being created and started, with timestamps indicating the duration of each step. ```bash [+] Running 8/8 ⠿ Network redpanda_network Created 0.0s ⠿ Volume "redpanda-quickstart_redpanda-0" Created 0.0s ⠿ Volume "redpanda-quickstart_redpanda-1" Created 0.0s ⠿ Volume "redpanda-quickstart_redpanda-2" Created 0.0s ⠿ Container redpanda-0 Started 0.3s ⠿ Container redpanda-console Started 0.6s ⠿ Container redpanda-1 Started 0.7s ⠿ Container redpanda-2 Started 0.7s ``` -------------------------------- ### GET /v1/redpanda-connect/pipelines Example Source: https://docs.redpanda.com/api/doc/cloud-dataplane/explorer/operation/operation-pipelineservice_listpipelines_authentication_id=authentication-auth0 An example of how to make a GET request to the /v1/redpanda-connect/pipelines endpoint. This example utilizes curl for demonstrating the request structure and parameters. ```curl curl -X GET "https://your-redpanda-instance.com/v1/redpanda-connect/pipelines?filter.name_contains={string}&filter.tags[string]={string}&page_size={integer}&page_token={string}" ``` -------------------------------- ### Redpanda Self-Managed Quickstart with Docker Compose Source: https://docs.redpanda.com/current/get-started/quickstarts Deploy a local Redpanda cluster using Docker Compose for development and testing. This quickstart provides a free 30-day Enterprise Edition license, extendable for another 30 days. It's suitable for beginners and experienced users to get hands-on with Redpanda. ```yaml # Example docker-compose.yml for Redpanda version: "3.7" services: redpanda: image: redpandadata/redpanda:v23.1.0 container_name: redpanda ports: - "8081:8081" - "9092:9092" - "2181:2181" command: "/usr/bin/rpk redpanda admin seatbelt \ --developer-mode \ --node-id 0 \ --set accept_enterprise_license=true \ --set "redpanda.tuning.num_seabees=0" \ --set "kafka_balance_controller.enable = true" \ --set "Pandaproxy.enabled=true" \ --set "Pandaproxy.num_threads=16" \ --set "Pandaproxy.client_api.port=8082" \ --set "Pandaproxy.admin_api.port=9642" environment: - "REDPANDA_SCOPE=developer" - "REDPANDA_KAFKA_LISTENERS=PLAINTEXT://:9092,SSL://:9093" - "REDPANDA_BROKERS=1" - "REDPANDA_ADVERTISED_LISTENERS=PLAINTEXT://localhost:9092,SSL://localhost:9093" - "REDPANDA_SCHEMA_REGISTRY_URL=http://localhost:8081" - "REDPANDA_SASL_MECHANISMS=SCRAM-SHA-256,SCRAM-SHA-512" - "REDPANDA_SECURITY_PROTOCOL_MAP=SCRAM_SHA_256:PLAINTEXT,SCRAM_SHA_512:PLAINTEXT,SSL:SSL" - "REDPANDA_SASL_ENABLED=true" - "REDPANDA_SASL_SCRAM_USERS=admin:password" - "REDPANDA_SASL_EXTERNAL_ENABLED=true" - "REDPANDA_AUTHORIZER_ENABLED=true" - "REDPANDA_AUTHORIZER_ALLOW_EVERYONE_ON_INIT=true" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_PRODUCER_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_PRODUCER_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_PRODUCER_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_PRODUCER_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_CONSUMER_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_CONSUMER_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_CONSUMER_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_CONSUMER_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_METADATA_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_METADATA_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_METADATA_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_METADATA_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_OFFSETS_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_OFFSETS_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_OFFSETS_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_OFFSETS_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_PRODUCE_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_PRODUCE_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_PRODUCE_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_PRODUCE_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_SIZE=1048576" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_MAX_BYTES=1048576" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_MIN_BYTES=1" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_BYTES=1048576" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCER_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCER_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCER_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCER_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_CONSUMER_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_CONSUMER_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_CONSUMER_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_CONSUMER_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_METADATA_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_OFFSETS_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_BATCH_TIME_MS=10" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_QUEUED_REQUESTS=10000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_PRODUCE_REQUEST_TIMEOUT_MS=60000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST_PREFETCH_MAX_FETCH_BATCH_SIZE=1000" - "REDPANDA_TUNING_KAFKA_REQUEST_SCHEDULER_MAX_FETCH_REQUEST ``` -------------------------------- ### rpk redpanda start Command Source: https://docs.redpanda.com/24.3/reference/rpk/rpk-redpanda/rpk-redpanda-start This section covers the basic usage of the 'rpk redpanda start' command and how to set up different modes for Redpanda. ```APIDOC ## rpk redpanda start This command starts the Redpanda cluster. It is not supported on macOS or Windows. ### Description Starts Redpanda with optional configuration modes and flags. ### Method CLI Command ### Endpoint N/A (CLI Command) ### Parameters #### Path Parameters None #### Query Parameters None #### Request Body None ### Request Example ```bash rpk redpanda start rpk redpanda start --mode dev-container ``` ### Response #### Success Response (0) Redpanda cluster starts successfully. #### Response Example ```text (Output indicating Redpanda is starting and running) ``` ## Setting up a mode It's possible to set up a mode for Redpanda to start. Currently, the `dev-container` mode is supported. To set up the `dev-container` mode, run: ```bash rpk redpanda start --mode dev-container ``` Mode uses well-known configuration properties for development or test environments. Bundled flags and cluster properties are applied when a mode is selected. ### Bundled Flags for `dev-container` mode: - `--overprovisioned` - `--reserve-memory 0M` - `--check=false` - `--unsafe-bypass-fsync` ### Bundled Cluster Properties for `dev-container` mode: - `write_caching_default: true` - `auto_create_topics_enabled: true` - `group_topic_partitions: 3` - `storage_min_free_bytes: 10485760 (10MiB)` - `topic_partitions_per_shard: 1000` - `fetch_reads_debounce_timeout: 10` After Redpanda starts, cluster properties can be modified using: ```bash rpk config set ``` ```