Resource Cleanup

Version: 17.07

Supported Since: 17.01

IPS expect its database to track all the ESB instances deployed on IPS. If there are running ESB instances that are not tracked by IPS database due to any inconsistency, those instances are identified as stale instances.

Stale Deployemnts

Sometimes (e.g. after a manual database clean-up) it may be necessary to remove ‘stale’ (unreferenced) Kubernetes artifacts (e.g. Kubernetes Deployments whose owning clusters have been removed from the database).

For removing such stale Deployments,

  • Open Resources > Stale Deployments.

S2I workflow
Figure 1. Stale Deployments

A list of stale Deployment entities in the Kubernetes cluster would be displayed, along with available metadata for each (e.g. the names of the clusters they used to belong to, and the names of Kubernetes Service entities associated with them)

  • Examine the list of Deployments displayed, to decide which ones should be deleted. Deletion of any of the displayed Deployments should be safe, as they are no longer being referenced by any of the existing clusters in the database. If you would like to delete

    • a single Deployment, click the Delete button against the required Deployment.

    • multiple Deployments:

      • Select the required Deployments using the check boxes against each entry.

      • Click the Delete button on the tab header.

Stale Services

Similar stale entity cleanup interfaces are available for Kubernetes Services and Pods as well, under Resources > Stale Services and Resources > Stale Pods respectively.

S2I workflow
Figure 2. Stale Services
In this topic
In this topic
Contact Us