1. Proposed title of this feature request

Enhance Central CR with Expanded Status Fields for Better Observability in RHACS

2. What is the nature and description of the request?

Currently, the Central Custom Resource (CR) in Red Hat Advanced Cluster Security (RHACS) only displays the Name and Age fields when queried using `oc get central` or `oc get central -o wide`. This provides limited visibility into the deployment status of the Central component.

This RFE proposes enhancing the oc get central output by including additional key fields such as:

Version: Displays the version of the deployed Central component.

adminPassword: Indicates the name of the secret containing the administrator password.

Progressing: Reflects whether changes are actively being rolled out.

Available: Confirms whether the Central instance is available.

Message: Provides a summary message such as "Your StackRox services are installed."

These enhancements will allow administrators to quickly assess the health and status of their RHACS Central deployment without needing additional commands or deep troubleshooting.

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

Operational Efficiency: Reduces the need for multiple commands (oc describe central, oc get pods, oc logs, etc.) to verify deployment success.

Faster Troubleshooting: Helps identify issues with deployment, rollout, or availability at a glance.

Improved User Experience: Provides key status information in a single view, making monitoring easier for admins managing RHACS.

Standardization with Other OpenShift Components: Aligns Central CR behavior with similar resources in OpenShift, which provide more status fields for improved observability.

4. Affected Packages or Components:

RHACS Operator (StackRox Central Operator)

RHACS Central Custom Resource (CR)

oc CLI Output for oc get central

Impact of Accepting this RFE:
If implemented, this RFE will significantly improve the administrative experience by making RHACS Central more observable and easier to manage. Users will have a quick, at-a-glance summary of deployment status, reducing troubleshooting efforts and enhancing operational efficiency.