> For the complete documentation index, see [llms.txt](https://docs.pynt.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pynt.io/documentation/security-testing-integrations/live-traffic-connectors/ebpf/pynt-for-kubernetes-quick-prerequisites-guide-for-the-scanner.md).

# Pynt for Kubernetes Quick Prerequisites Guide for the scanner

##

### Overview

The Pynt agent is the container that performs the Pynt scan inside your cluster. By default, it will be created in the **`pynt`namespace**. You can modify this namespace to fit your organization’s standards if needed.

### Access Control

* Make sure that **RBAC permissions** allow the Pynt agent in its namespace (default `pynt`) to access resources in the **other namespaces** where your APIs and microservices run.

### Networking (Egress)

* Ensure the agent can reach your APIs and required external endpoints (such as Pynt Cloud SaaS if applicable).
* DNS access must be allowed.
* If you run with strict NetworkPolicies, confirm that egress rules permit the Pynt agent to reach both your internal namespaces and any necessary external hosts.

### Resource Requirements

* The Pynt agent requires at least **2GB of memory requests** to run reliably. Ensure your cluster has sufficient resources before deploying.

***

**Tip**: Start with the default installation in the `pynt` namespace, validate connectivity, then adjust namespace, resources, and permissions as per your org’s policies.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pynt.io/documentation/security-testing-integrations/live-traffic-connectors/ebpf/pynt-for-kubernetes-quick-prerequisites-guide-for-the-scanner.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.