> 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/k8s-node-status-column-not-populated-after-hard-refresh-in-pf9-u.md).

# 'K8s Node Status' Column not Populated after Hard Refresh in PF9 UI

## Problem

When the UI loads for the first time or if we hard refresh the page, on the "**Nodes**" tab, the "**K8s Node Status**" column returns empty.

## Environment

* Platform9 Managed Kubernetes UI - 5.6.Z

## Cause

* The first refresh of the UI does not invoke the K8sAPI proxy call to get nodes from the K8s API server. It is invoked a few mins after a hard refresh.
* This is the reason we do not see a status under the "**K8s Node Status**" column. The engineering team is working on a fix and the same is being tracked under UX-2696

## Workaround

Manually click the '***Refresh'*** button in the UI which should load the status immediately.


---

# 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:

```
GET https://platform9.com/kb/pmk/solutions/k8s-node-status-column-not-populated-after-hard-refresh-in-pf9-u.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.