> 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/configuration-reference/startup-validation.md).

# Startup validation

Diagnose connection problems at startup.

{% hint style="info" %}
This feature is **disabled by default**. Set the corresponding `features` toggle to `enabled` in your pipeline file for the behavior described on this page to take effect.
{% endhint %}

Misconfigured bootstrap servers or credentials often surface as runtime errors deep into a replication run. Because connectivity to the source Kafka cluster and the target Kafka cluster is a prerequisite for everything else, therefore it is better to probe both at startup and fail fast when either is unreachable.

Enable `features.checkKafkaConnectionOnStartup` when validating a new deployment or after changing network or security settings. Other validation features — such as `features.validateControlTopicSettings` and `features.filterNonUpdatableTopicProperties` — can also fail at startup. On some managed Kafka offerings, these features can report false positives: vendor brokers may restrict admin APIs, hide internal topics, or expose topic configuration differently from open-source Apache Kafka. If connectivity and replication work outside those checks, disable the specific feature toggle rather than changing settings the vendor manages. For connection configuration, see [Kafka connectivity and authentication](https://docs.lenses.io/latest/k2k/configuration-reference/kafka-connectivity-authentication.md). For topic creation toggles, see [Topic creation](https://docs.lenses.io/latest/k2k/configuration-reference/topic-creation.md). For errors after replication has started, see [Troubleshooting](https://docs.lenses.io/latest/k2k/configuration-reference/troubleshooting.md) and [Pipeline tuning](https://docs.lenses.io/latest/k2k/configuration-reference/pipeline-tuning.md).

See also the [Validation checklist](https://docs.lenses.io/latest/k2k/runbooks/validation-checklist.md) for a pre-deployment workflow.

## Prerequisites

* [Kafka connectivity and authentication](https://docs.lenses.io/latest/k2k/configuration-reference/kafka-connectivity-authentication.md) configured

## Example

```yaml
name: "my_pipeline"
features:
  checkKafkaConnectionOnStartup: enabled
source:
  kafka:
    common:
      "bootstrap.servers": "source:9092"
    consumer:
      "group.id": "my-k2k-group"
target:
  kafka:
    common:
      "bootstrap.servers": "target:9092"
replication:
  - source:
      topic: "orders.*"
  - sink:
      topic: source
      partition: source
```

## Configuration keys

| Key                                          | Description                                                                             | Required | Default    | Used by    |
| -------------------------------------------- | --------------------------------------------------------------------------------------- | -------- | ---------- | ---------- |
| `features.checkKafkaConnectionOnStartup`     | Probe Kafka connectivity before starting replication                                    | No       | `disabled` | Replicator |
| `features.validateControlTopicSettings`      | Validate control topic configuration on startup                                         | No       | `enabled`  | Replicator |
| `features.filterNonUpdatableTopicProperties` | Probe which topic properties the target Kafka cluster accepts when auto creating topics | No       | `enabled`  | Replicator |


---

# 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/configuration-reference/startup-validation.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.
