Currently, OpenShift Cost Management generates optimization recommendations only for workloads managed by supported Kubernetes controllers such as Deployments and StatefulSets.

Pods managed by custom operators through CRDs (e.g., WebLogic Operator, custom domain CRs, etc.) do not receive optimization recommendations, even when:

• Resource requests/limits are defined

• Historical metrics are available

• Pods are long-running production workloads

This creates a visibility gap for enterprise workloads that are increasingly deployed via Operators and CRDs.

Business Impact

• Large enterprise applications (WebLogic, Kafka operators, database operators, etc.) are often deployed using CRDs.

• These workloads consume significant CPU and memory.

• Lack of optimization recommendations prevents:

• • Rightsizing

• • Cost savings identification

• • Capacity planning

• Creates inconsistency: standard workloads get insights, operator-managed workloads do not.