> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/solutions/kubelet-error--search-line-limits-were-exceeded--some-search-pat.md).

# Kubelet Error "Search Line limits were exceeded, some search paths have been omitted" is Causing Pod

## Problem

* Pods going in to CrashLoopBackOff state due to the DNS configuration error mentioned below.

{% tabs %}
{% tab title="Javascript" %}

```javascript
DNSConfigForming  2m58s (x5957 over 5d4h)  kubelet  Search Line limits were exceeded, some search paths have been omitted, the applied search line is
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes

## Cause

* Kubernetes allows for a maximum of six search domains.
* CoreDNS creates three search domains at run-time and not in the **`/etc/resolv.conf`** file, which leaves a maximum of three domains that can be defined in the **`/etc/resolv.conf`** file.
* If there are more than three user-defined search domains are included in the **`/etc/resolv.conf`** file on the cluster host then The **kubelet** agent writes excessive error messages to the kubelet log file.

## Resolution

* Need to make sure that there are no more than three search domains included in the **`/etc/resolv.conf`** file on the cluster host for which the error is logged in the kubelet logs.


---

# 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://platform9.com/kb/pmk/solutions/kubelet-error--search-line-limits-were-exceeded--some-search-pat.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.