> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/k2k/k2k-standalone-tool.md).

# K2K Standalone Tool

Administration tool for managing K2K committed offsets.

The K2K administration tool (`k2k-tool`) inspects replication state and adjusts consumer offsets on the target Kafka cluster. It provides a CLI and a web interface.

`k2k-tool` is bundled in the same container as K2K, so it is available in any K2K deployment.

## When to use it

Operators reach for `k2k-tool` during:

* Failover preparation and cutover — verify committed offsets before switching consumers
* Migration — inspect offset mapping progress per consumer group
* Incident investigation — compare committed vs latest offsets when lag is unexpected

For step-by-step procedures, see [Runbooks](/latest/k2k/runbooks.md).

{% hint style="danger" %}
Warning: Setting offsets should only be used when the K2K application has been stopped.

If the K2K application is running, the offset reset might not be applied as the application will continue to commit offsets, potentially overwriting the reset operation.
{% endhint %}

## Pipeline file

The YAML definition used by `k2k-tool` is a **subset** of the full K2K pipeline format. The same configuration file used for running K2K works without modification — the tool reads only the fields it needs.

Required configuration objects:

* `name`
* `source.kafka`
* `target.kafka`
* `replication`

## Documentation

| Topic             | Page                                                |
| ----------------- | --------------------------------------------------- |
| Web interface     | [Web UI](/latest/k2k/k2k-standalone-tool/web-ui.md) |
| Command reference | [CLI](/latest/k2k/k2k-standalone-tool/cli.md)       |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lenses.io/latest/k2k/k2k-standalone-tool.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.