> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prowler.com/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.prowler.com/feedback

```json
{
  "path": "/user-guide/providers/kubernetes/misc",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Miscellaneous

## Context Filtering in Prowler

Prowler will scan the active Kubernetes context by default.

To specify a different Kubernetes context for scanning, use the `--context` flag followed by the desired context name, for example:

```console theme={null}
prowler --context my-context
```

This ensures that Prowler analyzes the selected context or cluster for vulnerabilities and misconfigurations.

## Namespace Filtering

By default, `prowler` scans all namespaces within the specified context.

To limit the scan to specific namespaces, use the `--namespace` flag followed by the desired namespace names, separated by spaces: for example:

```console theme={null}
prowler --namespace namespace1 namespace2
```

## Proxy and TLS Verification

If your Kubernetes cluster is only accessible via an internal proxy, Prowler will respect the `HTTPS_PROXY` or `https_proxy` environment variable:

```console theme={null}
export HTTPS_PROXY=http://my.internal.proxy:8888
prowler kubernetes ...
```

If you need to skip TLS verification for internal proxies, you can set the `K8S_SKIP_TLS_VERIFY` environment variable:

```console theme={null}
export K8S_SKIP_TLS_VERIFY=true
prowler kubernetes ...
```

This will allow Prowler to connect to the cluster even if the proxy uses a self-signed certificate.

These environment variables are supported both when using an external `kubeconfig` and in in-cluster mode.