> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/solutions/podcidr-is-missing-from-the-node-spec-of-pmk-cluster.md).

# PodCIDR is Missing From The Node Spec of PMK Cluster

## Problem

* The **Citrix ingress controller** uses a feature called **feature-node-watch** to automatically configure route on the associated load balancer by reading the **podCIDR** information from the node spec.
* This feature does not work with the PMK cluster as it does not have **podCIDR** information included in node spec. This feature works fine with vanilla Kubernetes.

## Environment

* Platform9 Managed Kubernetes - v4.0 and Higher
* Citrix Ingress Controller

## Cause

* In Vanilla Kubernetes **Flannel** is deployed with the flag ***`--kube-subnet-mgr`***. This flag specifies that **Flannel** should contact Kubernetes API for subnet configuration on the node. For this reason, nodes resources are created with **podCIDR** in their spec.
* In PMK, **Flannel** is configured to get the subnet configuration from **etcd**. The PMK cluster **Flannel** CNI is brought up before Kubernetes control plane pods. Also, the flannel container runs outside of k8s and so it does not have an API server to talk to at the time of its bootstrap.

## Resolution

1. This is by design, we have created a feature request PMK8-I-138 to have the **podCIDR** information included in the node spec of the PMK clusters.
2. You can upvote this feature request by logging in to our [Ideas](https://ideas.platform9.com/ideas/PMK8-I-138) portal.


---

# 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://platform9.com/kb/pmk/solutions/podcidr-is-missing-from-the-node-spec-of-pmk-cluster.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.