---
title: "Kubernetes Objects Temporarily Disappear from the RealTheory Console"
slug: "kubernetes-objects-temporarily-disappear-from-the-realtheory-console"
updated: 2025-02-16T18:50:15Z
published: 2025-02-16T18:50:15Z
canonical: "resources.realtheory.io/kubernetes-objects-temporarily-disappear-from-the-realtheory-console"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://resources.realtheory.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Kubernetes Objects Temporarily Disappear from the RealTheory Console

## Background

The performance of the RealTheory Collector is impacted by the size of the cluster where the Collector is installed. On larger clusters, the CPU and memory requests configured for the `realtheorycollector` pod must be higher to ensure that the Collector has the resources it needs to function efficiently. If the requests are set too low, you might observe the following behaviors in the Console:

- Clusters and other objects temporarily disappear from the Console

- The `realtheorycollector` is restarting regularly due to a timeout in either the startup, readiness or liveness probes, often observed by a 'Service 503' (Service unavailable) error

## Solution

In the RealTheory Console, regenerate and redeploy the manifest for the RealTheory Collector in **Settings** > **Agent** > **Deployment** using the instructions in [Installing RealTheory in a Cluster](https://resources.realtheory.io/docs/installing-realtheory-in-a-cluster).

Make sure that you specify the approximate vCPU configuration of the cluster in **More options** > **Approximate cluster vCPU count** in the Deployment configuration form.

**Note:** If you are unsure of the cluster vCPU count, check the **Capacity** in the **Resource management** section of the **Metrics** tab of the cluster's information panel.