What is the nature and description of the request?
> This RFE aims to enhance the management of API deprecations and removals in OpenShift, ensuring smoother updates and reducing the risk of disruptions for namespace teams in multi-tenant clusters. The main request is to detect deprecated OpenShift APIs and Red Hat Operator CRDs for namespace administrators without cluster-admin permissions in an automated manner, such as integration in CI/CD pipelines.

There are multiple ways to achieve this goal:       

• Integrate this functionality in the oc binary
• Extend the functionality of APIRemovedInNextReleaseInUse and APIRemovedInNextEUSReleaseInUse to cover this usecase (include operator crds, make this alerts visible to the > namespace-admin, find some way to check this in an automated manner)
• Develop a standalone tool which covers this usecase
• Explore other potential methods to integrate this functionality directly into OpenShift
• Provide an official and regularly updated Red Hat versions.yaml file for Pluto (https://pluto.docs.fairwinds.com/#purpose), similar to the example provided in this Red Hat blog post (https://www.redhat.com/en/blog/detecting-deprecated-apis-with-pluto-in-your-ci/cd-workflows) a long with some documentation how to do api deprecation checking for namespace-admins with pluto NOTE: The above example only covers for deployments via helm.

Why does the customer need this? (List the business requirements here)

• Proactive Impact Assessment: Namespace teams need to assess the impact of upcoming OpenShift or operator updates on their resources to prevent deployment failures and production outages.
• Enhanced Visibility: Current alerts in the OpenShift console (e.g., APIRemovedInNextReleaseInUse) are only visible to platform administrators and do not include CRDs for Red Hat operators. Namespace administrators need similar visibility.
• Compliance and Stability: Ensuring that all resources are using supported API versions is crucial for maintaining compliance and stability within the OpenShift environment.
• Operational Efficiency: Reducing the risk of failed deployments due to deprecated APIs will improve overall operational efficiency and reduce downtime.
• Scalability and Automation: Relying on documentation alone is not sufficient, as it requires checking multiple documentation pages manually, which cannot be automated. Additionally, having each namespace administrator perform these checks individually does not scale well.

List any affected packages or components:

• OpenShift Console
• Red Hat Operator Lifecycle Manager (OLM)
• Custom Resource Definitions (CRDs) for Red Hat Operators
• Pluto (with Red Hat versions.yaml integration)
• Any existing tools or plugins related to API version management and detection