rpk topic: Manage, Produce & Consume
rpk topic is the rpk command group for all topic-level operations on a
Redpanda cluster. It wraps the Kafka protocol to create, inspect, alter, and
delete topics, and provides full-featured produce and consume commands with a
powerful percent-escape format language. All subcommands read connection config
from the active rpk profile or -X flags.
Quickstart
# 1. Create a 3-partition topic with replication factor 3
rpk topic create orders -p 3 -r 3
# 2. Create with configs set at creation time
rpk topic create events -p 6 -r 3 \
-c cleanup.policy=compact \
-c retention.ms=86400000
# 3. Produce three keyed JSON records — key and value on each line (Ctrl-D to finish)
# Note: when %k appears in --format, it reads the key from the input line and
# takes precedence over any -k flag. Use one mechanism or the other, not both.
rpk topic produce orders -f '%k %v{json}\n'
order-1 {"id":1,"status":"pending"}
order-2 {"id":2,"status":"shipped"}
order-3 {"id":3,"status":"delivered"}
# 4. Produce a single record inline via stdin redirect
printf 'hello world\n' | rpk topic produce orders
# 5. Consume from the beginning and stop at current end
rpk topic consume orders -o start
# 6. Consume last 5 records
rpk topic consume orders -o -5
# 7. Consume from a specific offset until current end
rpk topic consume orders -o 100:end
# 8. Consume in a named consumer group
rpk topic consume orders -g my-service
# 9. Describe the topic (summary + configs by default)
rpk topic describe orders
# 10. Describe including partition detail
rpk topic describe orders -p
# 11. Alter a topic config
rpk topic alter-config orders --set retention.ms=3600000
# 12. Delete a topic config key (revert to cluster default)
rpk topic alter-config orders --delete retention.ms
# 13. Add 2 more partitions
rpk topic add-partitions orders -n 2
# 14. List all topics
rpk topic list
# 15. Delete a topic
rpk topic delete orders
Subcommands
| Subcommand |
What it does |
create |
Create one or more topics with partitions, replicas, configs |
list (alias ls) |
List topics with partition and replica counts |
describe (alias info) |
Show topic summary, configs, and partition offsets |
describe-storage |
Show tiered-storage cloud/local status per partition |
alter-config |
Incrementally set, delete, append, or subtract config keys |
add-partitions |
Add N new partitions to an existing topic |
trim-prefix |
Move the log start offset forward, discarding old data |
analyze |
Measure batch rate and batch size over a time window |
delete |
Delete one or more topics |
produce |
Write records from stdin to a topic |
consume |
Read records from topics and print to stdout |
create
rpk topic create <TOPICS...> [flags]
| Flag |
Type |
Default |
Description |
-p, --partitions |
int32 |
-1 |
Number of partitions; -1 uses default_topic_partitions |
-r, --replicas |
int16 |
-1 |
Replication factor (must be odd); -1 uses default_topic_replications |
-c, --topic-config |
string (repeatable) |
|
key=value config pair, e.g. -c cleanup.policy=compact |
-d, --dry |
bool |
false |
Validate only; do not create |
--if-not-exists |
bool |
false |
Skip silently if topic already exists |
# Compact topic
rpk topic create audit-log -p 12 -r 3 -c cleanup.policy=compact
# Dry run
rpk topic create test-topic -p 3 -r 3 -d
list
rpk topic list [TOPICS...] [flags]
| Flag |
Default |
Description |
-d, --detailed |
false |
Show per-partition leader/replica detail |
-i, --internal |
false |
Include internal topics (e.g. __consumer_offsets) |
-r, --regex |
false |
Parse topic names as regex |
rpk topic list
rpk topic list -r '^orders.*'
rpk topic list -d
describe
rpk topic describe <TOPICS...> [flags]
By default prints the summary and configs sections. Sections:
| Flag |
Description |
-s, --print-summary |
Print topic name, partitions, replicas |
-c, --print-configs |
Print all config key/value/source pairs |
-p, --print-partitions |
Print per-partition leader, epoch, replicas, offsets |
-a, --print-all |
Print all three sections |
--stable |
Add last-stable-offset column (for transactional topics) |
-r, --regex |
Describe topics matching a regex |
rpk topic describe orders -a
rpk topic describe -r '^events.*' -a
alter-config
rpk topic alter-config <TOPICS...> [flags]
Supports four operations (all repeatable):
| Flag |
Operation |
-s, --set key=value |
Set a config value |
-d, --delete key |
Delete a key (revert to default) |
--append key=value |
Append to a list-of-values key |
--subtract key=value |
Remove from a list-of-values key |
--dry |
Validate only; do not apply |
--no-confirm |
Skip confirmation prompt |
# Enable tiered storage on a topic
rpk topic alter-config orders \
--set redpanda.remote.read=true \
--set redpanda.remote.write=true
# Change retention
rpk topic alter-config orders --set retention.ms=86400000
# Revert retention to cluster default
rpk topic alter-config orders --delete retention.ms
add-partitions
rpk topic add-partitions <TOPICS...> -n <N> [flags]
-n is required. Partitions can only be added, never removed.
rpk topic add-partitions orders -n 6
trim-prefix
Moves the log start offset (low watermark) forward, deleting segments before
the specified offset. Data before the new start offset is no longer readable.
rpk topic trim-prefix [TOPIC] -o <OFFSET> [flags]
| Flag |
Description |
-o, --offset |
Target offset (47, end, or @<timestamp>) |
-p, --partitions |
Comma-separated partition list (default: all) |
-f, --from-file |
File with topic/partition/offset rows |
--no-confirm |
Skip the confirmation prompt |
# Trim partition 0 to offset 1000
rpk topic trim-prefix orders -o 1000 -p 0
# Trim all partitions to a timestamp
rpk topic trim-prefix orders -o "@2024-01-01T00:00:00Z"
# Trim to the current end (delete everything)
rpk topic trim-prefix orders -o end
analyze
Consumes a time window of records and reports batch rate and size statistics.
rpk topic analyze <TOPICS...> [flags]
| Flag |
Default |
Description |
-t, --time-range |
-1m:end |
Time range to sample (e.g. -24h:end, -48h:-24h) |
--batches |
10 |
Minimum number of batches to consume per partition |
--timeout |
10s |
How long to run |
-a, --print-all |
false |
Print all output sections |
-s, --print-summary |
false |
Global summary |
--print-topics |
false |
Per-topic summary |
--print-partition-batch-rate |
false |
Batch rate percentiles |
--print-partition-batch-size |
false |
Batch size percentiles |
-r, --regex |
false |
Parse topic names as regex |
rpk topic analyze orders -t -1h:end -a
rpk topic analyze -r '^orders.*' -t -24h:end -s --print-topics
describe-storage
Requires the Admin API endpoint (from your profile or -X admin.hosts=...).
Shows tiered storage cloud vs. local bytes, segment counts, offsets, and sync
lag per partition. Not supported on Redpanda Cloud clusters (the Admin API is
not exposed there); all other rpk topic subcommands are.
rpk topic describe-storage <TOPIC> [flags]
| Flag |
Description |
-a, --print-all |
All sections |
-s, --print-summary |
Summary (name, mode, last-upload) |
-z, --print-size |
Cloud + local bytes and segment counts |
-y, --print-sync |
Upload lag, manifest sync |
-o, --print-offset |
Cloud and local start/last offsets |
-H, --human-readable |
Human-readable sizes/durations |
rpk topic describe-storage orders -a -H
Cloud storage modes: disabled, write_only, read_only, full,
read_replica, cloud_topic, cloud_topic_read_replica.
delete
rpk topic delete <TOPICS...> [flags]
-r, --regex parses topic names as regular expressions. Expressions are
anchored with ^ and $.
rpk topic delete old-topic
rpk topic delete -r '^test-.*'
produce
See Produce Reference for full detail.
rpk topic produce [TOPIC] [flags]
Key flags:
| Flag |
Default |
Description |
-f, --format |
%v\n |
Input record format (percent-escape syntax) |
-k, --key |
|
Fixed key for all records (parsed %k in format takes precedence) |
-H, --header |
|
key:value header (repeatable) |
-z, --compression |
snappy |
none, gzip, snappy, lz4, zstd |
--acks |
-1 |
-1=all ISR, 0=none, 1=leader |
-p, --partition |
-1 |
Direct-produce to this partition |
-Z, --tombstone |
false |
Produce empty value as null (tombstone) |
--schema-id |
|
Schema ID or topic (TopicName strategy) for value |
--schema-key-id |
|
Schema ID or topic for key |
--schema-type |
|
Fully-qualified Protobuf message type for value |
--schema-key-type |
|
Fully-qualified Protobuf message type for key |
--allow-auto-topic-creation |
false |
Auto-create the topic if it does not exist |
-o, --output-format |
Produced to partition %p at offset %o with timestamp %d.\n |
Line printed to stdout after each successful record |
--delivery-timeout |
0 |
Per-record delivery timeout (min 1s) |
--max-message-bytes |
-1 |
Max batch bytes before compression |
# Fixed key, newline-delimited values from stdin
rpk topic produce orders -k order-key
# Key and value separated by space
rpk topic produce orders -f '%k %v\n'
# Add headers
rpk topic produce orders -H source:backend -H env:prod
# Encode with schema registry (TopicName strategy)
rpk topic produce orders --schema-id=topic
# Tombstone
rpk topic produce orders -k deleted-key -Z
consume
See Consume Reference for full detail.
rpk topic consume <TOPICS...> [flags]
Key flags:
| Flag |
Default |
Description |
-f, --format |
json |
Output format (json or percent-escape string) |
-o, --offset |
start |
Where to start (and optionally end) consuming |
-p, --partitions |
|
Comma-separated list of partitions |
-g, --group |
|
Consumer group ID |
-n, --num |
0 |
Stop after N records (0 = unbounded) |
-r, --regex |
false |
Parse topic names as regex |
--read-committed |
false |
Only read committed offsets (for transactions) |
--print-control-records |
false |
Also print control records |
--use-schema-registry |
|
Decode with schema registry (key, value, or both) |
--meta-only |
false |
Print metadata but not record value (only affects -f json output) |
# Consume all records from beginning
rpk topic consume orders -o start
# Consume last 10 records
rpk topic consume orders -o -10
# Consume in a group, print key+value
rpk topic consume orders -g my-svc -f '%k %v\n'
# Consume a timestamp window
rpk topic consume orders -o @2024-01-01:1h
# Stop at current end
rpk topic consume orders -o :end
# Decode values via schema registry
rpk topic consume orders --use-schema-registry=value
Redpanda Cloud notes
rpk topic works against Redpanda Cloud clusters (Serverless, BYOC, Dedicated) over the Kafka API. Authenticate with rpk cloud login and wire your profile to the cluster (rpk cloud cluster select, or rpk profile create --from-cloud); plain rpk topic ... commands then target the Cloud cluster.
- All
rpk topic subcommands are supported on Cloud except rpk topic describe-storage, which needs the Admin API (not exposed by Redpanda Cloud).
- Automatic topic creation is disabled in Redpanda Cloud — create topics explicitly. BYOC/Dedicated clusters can opt in via the
auto_create_topics_enabled cluster property.
- Replication factor: Redpanda Cloud requires a minimum of 3 replicas; a topic created with
-r 1 is reset to 3.
- Message size: capped per topic by
max.message.bytes; the default and maximum differ by cluster type (Serverless caps are lower than BYOC/Dedicated). Check the Cloud "Topics Overview" page for current values rather than assuming self-managed defaults.
- Partition limits: Serverless clusters have a per-cluster partition cap (logical partitions, pre-replication) plus other usage limits (consumer groups, connections, ACLs, producer IDs) — see "Serverless usage limits" on the Serverless cluster-type page of the cloud docs. BYOC/Dedicated partition maxima depend on the usage tier — see the "BYOC Tiers and Regions" / "Dedicated Tiers and Regions" reference pages. These numbers change; do not hardcode them.
- Managed cluster defaults: cluster properties (e.g.
default_topic_partitions) are not user-configurable on Serverless, and on BYOC/Dedicated (AWS/GCP only) only a curated subset is settable.
- Tiered Storage on Cloud is enabled and configured by Redpanda by default. The Enterprise topic properties section below is written for self-managed clusters — note
rpk cluster license is also unsupported on Cloud.
- TODO (unverified): the cloud docs do not publish an explicit list of which topic-level configs are settable versus rejected/managed on Serverless. Before advising a specific
alter-config --set key on Serverless, verify against a live cluster or the Cloud UI.
Enterprise topic properties
Several Redpanda differentiators are configured as topic-level properties
through rpk topic create -c key=value or
rpk topic alter-config <topic> --set key=value. All of these require a valid
Enterprise Edition license; without one they cannot be enabled, and they enter
a restricted state on license expiration. Verify license status with
rpk cluster license info.
| Feature |
Key topic property(ies) |
Notes |
| Tiered Storage |
redpanda.remote.read, redpanda.remote.write, redpanda.remote.delete, redpanda.remote.recovery, redpanda.storage.mode=tiered, retention.local.target.{ms,bytes} |
Needs cluster cloud_storage_enabled=true; enabled when read+write both true. remote.recovery is create-only |
| Cloud Topics |
redpanda.cloud_topic.enabled, redpanda.storage.mode=cloud |
Object-storage-native topic; storage.mode=cloud is preferred |
| Iceberg Topics |
redpanda.iceberg.mode (disabled/key_value/value_schema_id_prefix/value_schema_latest), redpanda.iceberg.delete, redpanda.iceberg.partition.spec, redpanda.iceberg.target.lag.ms, redpanda.iceberg.invalid.record.action (drop/dlq_table) |
Needs cluster iceberg_enabled=true |
| Remote Read Replicas |
redpanda.remote.readreplica=<bucket> |
Mutually exclusive with remote.read/remote.write |
| Leader Pinning |
redpanda.leaders.preference (none / racks: / ordered_racks:) |
Needs enable_rack_awareness=true |
| Schema ID Validation |
redpanda.key.schema.id.validation, redpanda.value.schema.id.validation, redpanda.key.subject.name.strategy, redpanda.value.subject.name.strategy |
Needs cluster enable_schema_id_validation=redpanda or compat |
| Topic Deletion Control |
delete_topic_enable (cluster property) |
Guards rpk topic delete for all users |
# Tiered Storage
rpk topic alter-config orders --set redpanda.storage.mode=tiered
# Iceberg topic
rpk topic create txns --topic-config=redpanda.iceberg.mode=key_value
# Leader Pinning
rpk topic alter-config orders --set redpanda.leaders.preference=ordered_racks:A,B,C
# Schema ID validation
rpk topic alter-config events --set redpanda.value.schema.id.validation=true
See enterprise-topic-properties.md
for the full nested key list, accepted values, defaults, and expiration behavior.
Reference Directory
- produce.md:
rpk topic produce in depth — format percent-escape tokens, keys, headers, compression, acks, schema-registry encoding, tombstones, and worked examples.
- consume.md:
rpk topic consume in depth — all --offset forms (numeric, relative, timestamp, ranges), consumer groups, format tokens, schema-registry decoding, and worked examples.
- manage.md:
create, alter-config, add-partitions, describe, describe-storage, trim-prefix, analyze, and delete — with key config keys for retention, compaction, and tiered storage.
- enterprise-topic-properties.md: Enterprise-licensed topic properties set via
create -c / alter-config --set — Tiered Storage (redpanda.remote.*, redpanda.storage.mode, retention.local.target.*), Cloud Topics (redpanda.cloud_topic.enabled), Iceberg Topics (redpanda.iceberg.mode/delete/partition.spec/target.lag.ms/invalid.record.action), Remote Read Replicas (redpanda.remote.readreplica), Leader Pinning (redpanda.leaders.preference), and Schema ID Validation (redpanda.key/value.schema.id.validation, subject.name.strategy), with accepted values, defaults, and license-expiration behavior.
1---2name: rpk-topic3description: >-4 Manage Redpanda topics and produce or consume records from the CLI using the5 `rpk topic` command group. Use when creating or deleting topics with custom6 partitions, replication, or configs; altering topic configs or retention;7 adding partitions; trimming or deleting records; or using `rpk topic8 produce`/`consume` with the percent-escape format language, keys, headers,9 offsets, and schema-registry encoding/decoding. Also covers Enterprise topic10 properties, including Tiered Storage, Cloud Topics, Iceberg Topics, Remote11 Read Replicas, Leader Pinning, and server-side Schema ID Validation. Includes12 Redpanda Cloud notes on auth and per-tier limits; for Cloud login and profile13 setup, see /redpanda:rpk-cloud, and for Schema Registry details, see14 /redpanda:rpk-registry.15metadata:16 source: https://skillmd.com/skills/redpanda-data/rpk-topic17---1819# rpk topic: Manage, Produce & Consume2021`rpk topic` is the `rpk` command group for all topic-level operations on a22Redpanda cluster. It wraps the Kafka protocol to create, inspect, alter, and23delete topics, and provides full-featured produce and consume commands with a24powerful percent-escape format language. All subcommands read connection config25from the active rpk profile or `-X` flags.2627## Quickstart2829```bash30# 1. Create a 3-partition topic with replication factor 331rpk topic create orders -p 3 -r 33233# 2. Create with configs set at creation time34rpk topic create events -p 6 -r 3 \35 -c cleanup.policy=compact \36 -c retention.ms=864000003738# 3. Produce three keyed JSON records — key and value on each line (Ctrl-D to finish)39# Note: when %k appears in --format, it reads the key from the input line and40# takes precedence over any -k flag. Use one mechanism or the other, not both.41rpk topic produce orders -f '%k %v{json}\n'42order-1 {"id":1,"status":"pending"}43order-2 {"id":2,"status":"shipped"}44order-3 {"id":3,"status":"delivered"}4546# 4. Produce a single record inline via stdin redirect47printf 'hello world\n' | rpk topic produce orders4849# 5. Consume from the beginning and stop at current end50rpk topic consume orders -o start5152# 6. Consume last 5 records53rpk topic consume orders -o -55455# 7. Consume from a specific offset until current end56rpk topic consume orders -o 100:end5758# 8. Consume in a named consumer group59rpk topic consume orders -g my-service6061# 9. Describe the topic (summary + configs by default)62rpk topic describe orders6364# 10. Describe including partition detail65rpk topic describe orders -p6667# 11. Alter a topic config68rpk topic alter-config orders --set retention.ms=36000006970# 12. Delete a topic config key (revert to cluster default)71rpk topic alter-config orders --delete retention.ms7273# 13. Add 2 more partitions74rpk topic add-partitions orders -n 27576# 14. List all topics77rpk topic list7879# 15. Delete a topic80rpk topic delete orders81```8283## Subcommands8485| Subcommand | What it does |86|---|---|87| `create` | Create one or more topics with partitions, replicas, configs |88| `list` (alias `ls`) | List topics with partition and replica counts |89| `describe` (alias `info`) | Show topic summary, configs, and partition offsets |90| `describe-storage` | Show tiered-storage cloud/local status per partition |91| `alter-config` | Incrementally set, delete, append, or subtract config keys |92| `add-partitions` | Add N new partitions to an existing topic |93| `trim-prefix` | Move the log start offset forward, discarding old data |94| `analyze` | Measure batch rate and batch size over a time window |95| `delete` | Delete one or more topics |96| `produce` | Write records from stdin to a topic |97| `consume` | Read records from topics and print to stdout |9899## create100101```bash102rpk topic create <TOPICS...> [flags]103```104105| Flag | Type | Default | Description |106|---|---|---|---|107| `-p, --partitions` | int32 | `-1` | Number of partitions; `-1` uses `default_topic_partitions` |108| `-r, --replicas` | int16 | `-1` | Replication factor (must be odd); `-1` uses `default_topic_replications` |109| `-c, --topic-config` | string (repeatable) | | `key=value` config pair, e.g. `-c cleanup.policy=compact` |110| `-d, --dry` | bool | false | Validate only; do not create |111| `--if-not-exists` | bool | false | Skip silently if topic already exists |112113```bash114# Compact topic115rpk topic create audit-log -p 12 -r 3 -c cleanup.policy=compact116117# Dry run118rpk topic create test-topic -p 3 -r 3 -d119```120121## list122123```bash124rpk topic list [TOPICS...] [flags]125```126127| Flag | Default | Description |128|---|---|---|129| `-d, --detailed` | false | Show per-partition leader/replica detail |130| `-i, --internal` | false | Include internal topics (e.g. `__consumer_offsets`) |131| `-r, --regex` | false | Parse topic names as regex |132133```bash134rpk topic list135rpk topic list -r '^orders.*'136rpk topic list -d137```138139## describe140141```bash142rpk topic describe <TOPICS...> [flags]143```144145By default prints the `summary` and `configs` sections. Sections:146147| Flag | Description |148|---|---|149| `-s, --print-summary` | Print topic name, partitions, replicas |150| `-c, --print-configs` | Print all config key/value/source pairs |151| `-p, --print-partitions` | Print per-partition leader, epoch, replicas, offsets |152| `-a, --print-all` | Print all three sections |153| `--stable` | Add last-stable-offset column (for transactional topics) |154| `-r, --regex` | Describe topics matching a regex |155156```bash157rpk topic describe orders -a158rpk topic describe -r '^events.*' -a159```160161## alter-config162163```bash164rpk topic alter-config <TOPICS...> [flags]165```166167Supports four operations (all repeatable):168169| Flag | Operation |170|---|---|171| `-s, --set key=value` | Set a config value |172| `-d, --delete key` | Delete a key (revert to default) |173| `--append key=value` | Append to a list-of-values key |174| `--subtract key=value` | Remove from a list-of-values key |175| `--dry` | Validate only; do not apply |176| `--no-confirm` | Skip confirmation prompt |177178```bash179# Enable tiered storage on a topic180rpk topic alter-config orders \181 --set redpanda.remote.read=true \182 --set redpanda.remote.write=true183184# Change retention185rpk topic alter-config orders --set retention.ms=86400000186187# Revert retention to cluster default188rpk topic alter-config orders --delete retention.ms189```190191## add-partitions192193```bash194rpk topic add-partitions <TOPICS...> -n <N> [flags]195```196197`-n` is required. Partitions can only be added, never removed.198199```bash200rpk topic add-partitions orders -n 6201```202203## trim-prefix204205Moves the log start offset (low watermark) forward, deleting segments before206the specified offset. Data before the new start offset is no longer readable.207208```bash209rpk topic trim-prefix [TOPIC] -o <OFFSET> [flags]210```211212| Flag | Description |213|---|---|214| `-o, --offset` | Target offset (`47`, `end`, or `@<timestamp>`) |215| `-p, --partitions` | Comma-separated partition list (default: all) |216| `-f, --from-file` | File with topic/partition/offset rows |217| `--no-confirm` | Skip the confirmation prompt |218219```bash220# Trim partition 0 to offset 1000221rpk topic trim-prefix orders -o 1000 -p 0222223# Trim all partitions to a timestamp224rpk topic trim-prefix orders -o "@2024-01-01T00:00:00Z"225226# Trim to the current end (delete everything)227rpk topic trim-prefix orders -o end228```229230## analyze231232Consumes a time window of records and reports batch rate and size statistics.233234```bash235rpk topic analyze <TOPICS...> [flags]236```237238| Flag | Default | Description |239|---|---|---|240| `-t, --time-range` | `-1m:end` | Time range to sample (e.g. `-24h:end`, `-48h:-24h`) |241| `--batches` | `10` | Minimum number of batches to consume per partition |242| `--timeout` | `10s` | How long to run |243| `-a, --print-all` | false | Print all output sections |244| `-s, --print-summary` | false | Global summary |245| `--print-topics` | false | Per-topic summary |246| `--print-partition-batch-rate` | false | Batch rate percentiles |247| `--print-partition-batch-size` | false | Batch size percentiles |248| `-r, --regex` | false | Parse topic names as regex |249250```bash251rpk topic analyze orders -t -1h:end -a252rpk topic analyze -r '^orders.*' -t -24h:end -s --print-topics253```254255## describe-storage256257Requires the Admin API endpoint (from your profile or `-X admin.hosts=...`).258Shows tiered storage cloud vs. local bytes, segment counts, offsets, and sync259lag per partition. Not supported on Redpanda Cloud clusters (the Admin API is260not exposed there); all other `rpk topic` subcommands are.261262```bash263rpk topic describe-storage <TOPIC> [flags]264```265266| Flag | Description |267|---|---|268| `-a, --print-all` | All sections |269| `-s, --print-summary` | Summary (name, mode, last-upload) |270| `-z, --print-size` | Cloud + local bytes and segment counts |271| `-y, --print-sync` | Upload lag, manifest sync |272| `-o, --print-offset` | Cloud and local start/last offsets |273| `-H, --human-readable` | Human-readable sizes/durations |274275```bash276rpk topic describe-storage orders -a -H277```278279Cloud storage modes: `disabled`, `write_only`, `read_only`, `full`,280`read_replica`, `cloud_topic`, `cloud_topic_read_replica`.281282## delete283284```bash285rpk topic delete <TOPICS...> [flags]286```287288`-r, --regex` parses topic names as regular expressions. Expressions are289anchored with `^` and `$`.290291```bash292rpk topic delete old-topic293rpk topic delete -r '^test-.*'294```295296## produce297298See [Produce Reference](references/produce.md) for full detail.299300```bash301rpk topic produce [TOPIC] [flags]302```303304Key flags:305306| Flag | Default | Description |307|---|---|---|308| `-f, --format` | `%v\n` | Input record format (percent-escape syntax) |309| `-k, --key` | | Fixed key for all records (parsed `%k` in format takes precedence) |310| `-H, --header` | | `key:value` header (repeatable) |311| `-z, --compression` | `snappy` | `none`, `gzip`, `snappy`, `lz4`, `zstd` |312| `--acks` | `-1` | `-1`=all ISR, `0`=none, `1`=leader |313| `-p, --partition` | `-1` | Direct-produce to this partition |314| `-Z, --tombstone` | false | Produce empty value as null (tombstone) |315| `--schema-id` | | Schema ID or `topic` (TopicName strategy) for value |316| `--schema-key-id` | | Schema ID or `topic` for key |317| `--schema-type` | | Fully-qualified Protobuf message type for value |318| `--schema-key-type` | | Fully-qualified Protobuf message type for key |319| `--allow-auto-topic-creation` | false | Auto-create the topic if it does not exist |320| `-o, --output-format` | `Produced to partition %p at offset %o with timestamp %d.\n` | Line printed to stdout after each successful record |321| `--delivery-timeout` | `0` | Per-record delivery timeout (min 1s) |322| `--max-message-bytes` | `-1` | Max batch bytes before compression |323324```bash325# Fixed key, newline-delimited values from stdin326rpk topic produce orders -k order-key327328# Key and value separated by space329rpk topic produce orders -f '%k %v\n'330331# Add headers332rpk topic produce orders -H source:backend -H env:prod333334# Encode with schema registry (TopicName strategy)335rpk topic produce orders --schema-id=topic336337# Tombstone338rpk topic produce orders -k deleted-key -Z339```340341## consume342343See [Consume Reference](references/consume.md) for full detail.344345```bash346rpk topic consume <TOPICS...> [flags]347```348349Key flags:350351| Flag | Default | Description |352|---|---|---|353| `-f, --format` | `json` | Output format (`json` or percent-escape string) |354| `-o, --offset` | `start` | Where to start (and optionally end) consuming |355| `-p, --partitions` | | Comma-separated list of partitions |356| `-g, --group` | | Consumer group ID |357| `-n, --num` | `0` | Stop after N records (0 = unbounded) |358| `-r, --regex` | false | Parse topic names as regex |359| `--read-committed` | false | Only read committed offsets (for transactions) |360| `--print-control-records` | false | Also print control records |361| `--use-schema-registry` | | Decode with schema registry (`key`, `value`, or both) |362| `--meta-only` | false | Print metadata but not record value (only affects `-f json` output) |363364```bash365# Consume all records from beginning366rpk topic consume orders -o start367368# Consume last 10 records369rpk topic consume orders -o -10370371# Consume in a group, print key+value372rpk topic consume orders -g my-svc -f '%k %v\n'373374# Consume a timestamp window375rpk topic consume orders -o @2024-01-01:1h376377# Stop at current end378rpk topic consume orders -o :end379380# Decode values via schema registry381rpk topic consume orders --use-schema-registry=value382```383384## Redpanda Cloud notes385386`rpk topic` works against Redpanda Cloud clusters (Serverless, BYOC, Dedicated) over the Kafka API. Authenticate with `rpk cloud login` and wire your profile to the cluster (`rpk cloud cluster select`, or `rpk profile create --from-cloud`); plain `rpk topic ...` commands then target the Cloud cluster.387388- **All `rpk topic` subcommands are supported on Cloud except `rpk topic describe-storage`**, which needs the Admin API (not exposed by Redpanda Cloud).389- **Automatic topic creation is disabled** in Redpanda Cloud — create topics explicitly. BYOC/Dedicated clusters can opt in via the `auto_create_topics_enabled` cluster property.390- **Replication factor**: Redpanda Cloud requires a minimum of 3 replicas; a topic created with `-r 1` is reset to 3.391- **Message size**: capped per topic by `max.message.bytes`; the default and maximum differ by cluster type (Serverless caps are lower than BYOC/Dedicated). Check the Cloud "Topics Overview" page for current values rather than assuming self-managed defaults.392- **Partition limits**: Serverless clusters have a per-cluster partition cap (logical partitions, pre-replication) plus other usage limits (consumer groups, connections, ACLs, producer IDs) — see "Serverless usage limits" on the Serverless cluster-type page of the cloud docs. BYOC/Dedicated partition maxima depend on the usage tier — see the "BYOC Tiers and Regions" / "Dedicated Tiers and Regions" reference pages. These numbers change; do not hardcode them.393- **Managed cluster defaults**: cluster properties (e.g. `default_topic_partitions`) are not user-configurable on Serverless, and on BYOC/Dedicated (AWS/GCP only) only a curated subset is settable.394- **Tiered Storage on Cloud** is enabled and configured by Redpanda by default. The Enterprise topic properties section below is written for self-managed clusters — note `rpk cluster license` is also unsupported on Cloud.395- **TODO (unverified)**: the cloud docs do not publish an explicit list of which topic-level configs are settable versus rejected/managed on Serverless. Before advising a specific `alter-config --set` key on Serverless, verify against a live cluster or the Cloud UI.396397## Enterprise topic properties398399Several Redpanda differentiators are configured as **topic-level properties**400through `rpk topic create -c key=value` or401`rpk topic alter-config <topic> --set key=value`. All of these **require a valid402Enterprise Edition license**; without one they cannot be enabled, and they enter403a restricted state on license expiration. Verify license status with404`rpk cluster license info`.405406| Feature | Key topic property(ies) | Notes |407|---|---|---|408| Tiered Storage | `redpanda.remote.read`, `redpanda.remote.write`, `redpanda.remote.delete`, `redpanda.remote.recovery`, `redpanda.storage.mode=tiered`, `retention.local.target.{ms,bytes}` | Needs cluster `cloud_storage_enabled=true`; enabled when read+write both `true`. `remote.recovery` is create-only |409| Cloud Topics | `redpanda.cloud_topic.enabled`, `redpanda.storage.mode=cloud` | Object-storage-native topic; `storage.mode=cloud` is preferred |410| Iceberg Topics | `redpanda.iceberg.mode` (`disabled`/`key_value`/`value_schema_id_prefix`/`value_schema_latest`), `redpanda.iceberg.delete`, `redpanda.iceberg.partition.spec`, `redpanda.iceberg.target.lag.ms`, `redpanda.iceberg.invalid.record.action` (`drop`/`dlq_table`) | Needs cluster `iceberg_enabled=true` |411| Remote Read Replicas | `redpanda.remote.readreplica=<bucket>` | Mutually exclusive with `remote.read`/`remote.write` |412| Leader Pinning | `redpanda.leaders.preference` (`none` / `racks:` / `ordered_racks:`) | Needs `enable_rack_awareness=true` |413| Schema ID Validation | `redpanda.key.schema.id.validation`, `redpanda.value.schema.id.validation`, `redpanda.key.subject.name.strategy`, `redpanda.value.subject.name.strategy` | Needs cluster `enable_schema_id_validation=redpanda` or `compat` |414| Topic Deletion Control | `delete_topic_enable` (cluster property) | Guards `rpk topic delete` for all users |415416```bash417# Tiered Storage418rpk topic alter-config orders --set redpanda.storage.mode=tiered419420# Iceberg topic421rpk topic create txns --topic-config=redpanda.iceberg.mode=key_value422423# Leader Pinning424rpk topic alter-config orders --set redpanda.leaders.preference=ordered_racks:A,B,C425426# Schema ID validation427rpk topic alter-config events --set redpanda.value.schema.id.validation=true428```429430See [enterprise-topic-properties.md](references/enterprise-topic-properties.md)431for the full nested key list, accepted values, defaults, and expiration behavior.432433## Reference Directory434435- [produce.md](references/produce.md): `rpk topic produce` in depth — format percent-escape tokens, keys, headers, compression, acks, schema-registry encoding, tombstones, and worked examples.436- [consume.md](references/consume.md): `rpk topic consume` in depth — all `--offset` forms (numeric, relative, timestamp, ranges), consumer groups, format tokens, schema-registry decoding, and worked examples.437- [manage.md](references/manage.md): `create`, `alter-config`, `add-partitions`, `describe`, `describe-storage`, `trim-prefix`, `analyze`, and `delete` — with key config keys for retention, compaction, and tiered storage.438- [enterprise-topic-properties.md](references/enterprise-topic-properties.md): Enterprise-licensed topic properties set via `create -c` / `alter-config --set` — Tiered Storage (`redpanda.remote.*`, `redpanda.storage.mode`, `retention.local.target.*`), Cloud Topics (`redpanda.cloud_topic.enabled`), Iceberg Topics (`redpanda.iceberg.mode/delete/partition.spec/target.lag.ms/invalid.record.action`), Remote Read Replicas (`redpanda.remote.readreplica`), Leader Pinning (`redpanda.leaders.preference`), and Schema ID Validation (`redpanda.key/value.schema.id.validation`, `subject.name.strategy`), with accepted values, defaults, and license-expiration behavior.