rpk-group

Manage Kafka consumer groups via rpk group subcommands.

6|3|Updated May 31, 2026
One-click install
npx skills add https://github.com/redpanda-data/skills --skill rpk-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rpk-group
Source: https://github.com/redpanda-data/skills/tree/main/skills/rpk-group
Command: npx skills add https://github.com/redpanda-data/skills --skill rpk-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

rpk group solves the challenge of managing Kafka consumer groups by providing commands to observe lag, membership, and offsets, enabling safer operations in production Redpanda clusters.

Core Features & Use Cases

  • Inspect and describe consumer groups to determine lag and membership, including per-partition details.
  • Reset or seek group offsets (to start, end, timestamp, or another group's commits) with safety checks.
  • Delete committed offsets for specific partitions or delete entire groups, with guardrails to protect data and ensure recoverability.

Quick Start

Describe a group and inspect its lag, then reset to the start if needed.

Frequently Asked Questions about rpk-group

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Kafka consumer group lag in a Redpanda cluster?

Use rpk group describe to inspect Kafka consumer group lag in Redpanda, viewing per-partition details, membership, and committed offsets for production clusters.

What is the best way to reset Kafka consumer group offsets to a specific timestamp?

Reset Kafka consumer group offsets using rpk group seek to move to the start, end, a specific timestamp, or another group's commits, with safety checks enforcing an empty group.

Can I delete committed offsets for specific partitions in a Kafka consumer group?

Yes, you can delete committed offsets for specific Kafka partitions using rpk group offset-delete, which applies guardrails to protect data and ensure recoverability during production operations.

Why does rpk group require an empty consumer group before resetting offsets?

rpk group enforces an empty consumer group for offset resets to ensure safety, preventing active consumers from processing messages out of order or missing data during the reset operation.

How do I manage multiple Kafka consumer groups at once in Redpanda?

Manage multiple Kafka consumer groups in Redpanda by using rpk group commands with regex to filter, describe, and delete several groups simultaneously across production clusters.