> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-container/kubernetes-integration/manually-import-kubernetes-workload-projects.md).
# Manually import Kubernetes workload Projects
Using the same integration ID, you can import multiple clusters to one Snyk Organization by giving clusters a unique cluster name during installation.
You can also import one cluster to multiple Snyk Organizations in manual import by [cloning an integration across your Snyk organizations](/platform-administration/snyk-broker/classic-broker/clone-an-integration-across-your-snyk-organizations.md), so the integrations have the same integration ID.
One Snyk Organization has a limit of 25,000 Projects. For more information, contact your Snyk admin.
## Prerequisites for manually importing Kubernetes workload Projects
You must first have an account with Snyk and be onboarded to your Organization by an administrator.
In addition, you must configure the integration between Snyk and your Kubernetes environment per Organization. To ensure the integration is configured, ensure you have an Integration ID. For more information, see [Enable the Kubernetes integration](/scan-fix-and-prevent/scan-with-snyk/snyk-container/kubernetes-integration/overview-of-kubernetes-integration/enable-the-kubernetes-integration.md).
Next:
1. Deploy the Snyk Controller in your Kubernetes cluster.
2. Deploy the Kubernetes workloads that you want to import into the Kubernetes cluster.
## Manually add Kubernetes workloads
In the Snyk Web UI, navigate to the **Projects** page, and click **Add projects** at the top of the page. From the list of Projects, select **Kubernetes**.
On the import screen that appears, all namespaces from the Kubernetes environment are displayed on the left, and the relevant namespace workloads are displayed on the right.
Kubernetes workloads import screen
Snyk purposely ignores scanning certain namespaces that Snyk believes are internal to Kubernetes (any namespace starting with kube-\*). Therefore, those namespaces do not appear in the list, and neither do the workloads that those namespaces contain. You can see the full list of ignored namespaces in the [kubernetes-monitor internal-workspaces file](https://github.com/snyk/kubernetes-monitor/blob/master/src/supervisor/watchers/internal-namespaces.ts).
You can configure the list by adding the following code to Helm when you are setting up the snyk-monitor:
```
--set excludedNamespaces={kube-node-lease,local-path-storage,some_namespace}
```
Select one or multiple namespaces from the left side of the screen, and for each namespace, select one or multiple workloads to import from the right side of the screen.
Selecting namespaces from the Kubernetes workloads import screen
Next, click **Add selected workloads** from the top right of the screen. When the import completes, the **Projects** page loads, and all the workloads that you have imported appear with a unique Kubernetes icon.
Each item is named according to its Kubernetes metadata:
\/\/\
In the **Projects** list, you can filter Kubernetes Projects.
---
# 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.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-container/kubernetes-integration/manually-import-kubernetes-workload-projects.md?ask=&goal=
```
`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.