> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/kubernetes-security/kspm-limitations-and-system-components/configure-kubernetes-connector-resource-limits.md).

# Configure Kubernetes Connector resource limits

The Kubernetes Connector consists of multiple components that require CPU and memory allocation. Follow these steps to set limits that align with your resource needs.

1. **Download the values file**

   From the Kubernetes Connect wizard, click **Generate** to download the `K8s-security-profile-panw-DATE.values.yaml` file from the first step.
2. **Adjust workload requests and limits**\
   Edit the file to adjust the requests and limits of the workloads.\
   Use this example as a reference when configuring your file:

```yaml
konnector-template:
  enabled: true

# ============================================================================
# Core — Cortex Manager (k8sConnector) — full override
# ============================================================================
coreValues:
  resources:
    k8sConnector:
      overrides:
        requests:
          cpu: "300m"
          memory: "256Mi"
        limits:
          cpu: "500m"
          memory: "512Mi"

# ============================================================================
# Monitoring — OpenTelemetry Collector (otel) — full override
# ============================================================================
monitoringValues:
  enabled: true
  resources:
    otel:
      overrides:
        requests:
          cpu: "100m"
          memory: "200Mi"
        limits:
          cpu: "300m"
          memory: "400Mi"

# ============================================================================
# Posture — admission controller, orchestrator, and spawned jobs
# ============================================================================
postureValues:
  enabled: true

  admissionController:
    enabled: true
    failurePolicy: Ignore

  jobOrchestrator:
    scanIntervalHours: 12

  resources:
    # Admission Controller — full override
    admissionController:
      overrides:
        requests:
          cpu: "100m"
          memory: "300Mi"
        limits:
          cpu: "300m"
          memory: "600Mi"

    # Job Orchestrator — CPU request + CPU limit only
    # (memory keeps defaults: requests.memory=75Mi, limits.memory=100Mi)
    jobOrchestrator:
      overrides:
        requests:
          cpu: "50m" # was 25m
        limits:
          cpu: "100m" # was 50m

    # Resources for jobs spawned by the orchestrator
    jobResources:
      # Host Scanner — memory limit only
      # (CPU and memory request keep defaults)
      host-scanner:
        overrides:
          limits:
            memory: "8Gi" # was 4.5Gi

      # Inventory Collector — CPU request + CPU limit only
      # (memory keeps defaults: requests.memory=50Mi, limits.memory=100Mi)
      inventory-collector:
        overrides:
          requests:
            cpu: "50m" # was 25m
          limits:
            cpu: "100m" # was 50m

      # Compliance K8s Scanner — full override
      compliance-k8s-scanner:
        overrides:
          requests:
            cpu: "300m"
            memory: "100Mi"
          limits:
            cpu: "750m"
            memory: "200Mi"

      # Scan Result Publisher — full override
      scan-result-publisher:
        overrides:
          requests:
            cpu: "50m"
            memory: "100Mi"
          limits:
            cpu: "100m"
            memory: "750Mi"

      # Node VM Discovery — full override
      node-vm-discovery:
        overrides:
          requests:
            cpu: "30m"
            memory: "100Mi"
          limits:
            cpu: "100m"
            memory: "200Mi"
```

3. **Deploy the Kubernetes Connector**\
   Deploy the Kubernetes Connector using Helm:

```bash
helm upgrade --install konnector oci://us-central1-docker.pkg.dev/qa2-test-YYY/agent docker/helm/konnector-launcher \
  --wait-for-jobs \
  --create-namespace \
  --namespace panw \
  --values K8s-security-profile-panw-DATE.values.yaml \
  --set-file konnector-upgrader.rawValuesContent=K8s-security-profile-panw-DATE.values.yaml
```


---

# 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://cortex-docs.paloaltonetworks.com/kubernetes-security/kspm-limitations-and-system-components/configure-kubernetes-connector-resource-limits.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.