> 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/generic/frequently-asked-questions/increased-api-calls-to-qbert-causing-high-cpu-usage-for-keystone.md).

# Increased API calls To Qbert Causing High CPU Usage For Keystone Pods.

## Problem

A high number of API calls to Qbert, causing high traffic towards the Keystone pod, resulting in CPU limit exhaustion for the Keystone pods followed by authentication issues causing the downtime.

## Environment

* Platform9 Managed Kubernetes - v5.6 and Higher

## Cause

When a customer downloads a kubeconfig for any cluster, Platform9 provide two contexts as a part of that kubeconfig.

1. The first one is named “**default**” which has a server entry for the K8s VIP.
2. The second one is named “**\<cluster\_name>-pf9**” and that routes all API calls through the Qbert proxy.

When customer downloads the kubeconfig and start using the context that has the cluster name, there are a lot of API calls going to Qbert and it eventually increases the load on keystone pod since each API call needs to be authenticated.

## Workaround

Only use **default** context within the kubeconfig to access the cluster. This will avoid traffic to Keystone pod and further avoid authentication issues causing the downtime.

## Additional Information

An Internal jira PMK-5886 has been filed to ensure **\<cluster\_name>-pf9** is removed from the downloaded kubeconfig so as to avoid accidental usage with **\<cluster\_name>-pf9** context causing the resource spike of Keystone pod\*\*.\*\* To track progress of this jira, please open a support ticket mentioning the JiraID- PMK-5886..


---

# 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://platform9.com/kb/generic/frequently-asked-questions/increased-api-calls-to-qbert-causing-high-cpu-usage-for-keystone.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.