# Reusing the K2K configuration The K2K Offset Mapping application uses the same YAML configuration format as the standard K2K pipeline. Its configuration extends most of the base K2K Config definitions while omitting others that are not applicable. Any valid K2K pipeline configuration can be used as a starting point for the Offset Mapping application. In practice, this means an existing K2K configuration file can serve as a base. Only the additional fields specific to offset mapping need to be provided on top of the existing configuration to enable the feature.

Property/Section	Present in K2K	Present in K2K Offset Mapping	Required
`name`	✅	✅	true
`features.autoCreateControlTopics`	✅	✅	false
`features.applyMappingsGuards`	➖	✅	false
`license.*`	✅	✅	false
`errorHandling.onMultipleTargetCommittedOffsets`	➖	✅	false
`errorHandling.onActiveConsumerGroupCommit`	➖	✅	false
`source.kafka.common`	✅	✅	true
`source.kafka.admin`	✅	✅	true
`target.kafka.common`	✅	✅	true
`target.kafka.producer`	✅	✅	true
`target.kafka.admin`	✅	✅	true
`target.kafka.consumer`	✅	✅	true
`metrics.prefix.targetConsumer`	➖	✅	false
`metrics.prefix.targetProducer`	➖	✅	false
`metrics.prefix.offsetMappingApp`	➖	✅	false

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.lenses.io/latest/k2k/k2k-offset-mapping/reusing-the-k2k-configuration.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.