> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/private-cloud-director/kubernetes-clusters/k8s-pre-requisites.md).

# Pre-requisites

Before deploying Kubernetes Clusters with <code class="expression">space.vars.product\_acronym</code>, ensure the following prerequisites are met:

Infrastructure & Environment

* <code class="expression">space.vars.product\_acronym</code> [Virtualized Cluster Blueprint](/private-cloud-director/virtualized-clusters/virtualized-cluster-blueprint.md) configured with Hosts and ready to create Virtual Machines
* Storage Configured in Virtualized Cluster
* Enough resource capacity and quota available to your user to create VMs in your <code class="expression">space.vars.product\_acronym</code> Tenant.

Networking & Connectivity

* [Networks And Ports](/private-cloud-director/virtualized-networking/networks-and-ports.md) or [Physical Network](/private-cloud-director/virtualized-networking/physical-network.md) created in <code class="expression">space.vars.product\_acronym</code> for Kubernetes Node VMs networking.
* The network type needs to be "Managed Network". "Layer 2 Networks" are not supported.
* The default pod CIDR for <code class="expression">space.vars.product\_acronym</code> Kubernetes cluster is 10.244.0.0/16 and default service CIDR is 10.96.0.0/16. These must not overlap with <code class="expression">space.vars.product\_acronym</code> Virtualization private networks.
* "Port Security" must be enabled on the underlying network to allow for proper traffic filtering and security group application.
* Clusters require a direct connection to the internet. Please note that network proxies are not supported at this time.
* Ensure the following domains are permitted through the firewall: The management plane FQDN `<management plane FQDN>` (e.g. `customer.app.staging-pcd.platform9.com`), `quay.io` , and `registry.k8s.io` .

Images & Access

* Cluster API compliant Operating System Image uploaded into [Image Library and Images](/private-cloud-director/images-and-image-library/image-library---images.md) specific to Kubernetes version you want to deploy. See more details here: [Kubernetes Operating System Image Management](/private-cloud-director/kubernetes-clusters/kubernetes-operating-system-image-management.md)
* An SSH key created in <code class="expression">space.vars.product\_acronym</code>. You select this key when creating the cluster, and it is bootstrapped into the worker nodes so you can access them via CLI. Go to the **Virtual Machines** > **SSH Keys** page and add your key here by clicking on Import SSH Key.


---

# 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://docs.platform9.com/private-cloud-director/kubernetes-clusters/k8s-pre-requisites.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.