Handling Native Kubernetes Workload Objects

[finally-fancy]

Description Busula should introduce a configuration option that allows users to selectively disable or filter out specific Kubernetes resources, such as Pods, Deployments, and ReplicaSets, at both the API query level and the UI rendering level. This can be easily achieved if native Kubernetes objects are handled like any CRD object, as proposed, by reading the OpenAPI 3.0 schema instead of the CRD's spec. In this case, native Kubernetes objects are treated the same as CRDs, allowing them to be disabled in the same way as CRD objects.

Reasons In Busula, Kubernetes workload objects like Pods, Deployments, and ReplicaSets are typically shown by default. However, in certain use cases, such as when using KCP (Kubernetes Control Plane) with specialized environments, showing these standard Kubernetes workload objects is unnecessary or even irrelevant. This can result in cluttered UIs with unnecessary data and unwanted API calls that return HTTP 404 errors when Busula attempts to query objects that don't exist or aren’t supported by the KCP API-Server.