Goal Summary

This feature will enhance the oc get central command by adding key status fields directly to the output. This will allow administrators to quickly and efficiently assess the health and status of their RHACS Central deployments, reducing the need for multiple commands and speeding up troubleshooting.

Goals and Expected User Outcomes

The primary user, a DevOps Engineer or Site Reliability Engineer (SRE), will now be able to view critical information about the Central instance directly from the oc get central command. This expands the existing functionality by enriching the output of this core oc command.

• Version: The user can see the deployed version of the Central component.
• adminPassword: The user can identify the secret that holds the admin password.
• Progressing: The user can determine if an update or change is currently in progress.
• Available: The user can quickly confirm if the Central instance is operational and available, derived from the status of its underlying workloads.
• Message: The user receives a clear, concise summary message regarding the state of the deployment (e.g., "Your StackRox services are installed.").

Acceptance Criteria

• The oc get central command must display the VERSION, ADMINPASSWORD, PROGRESSING, AVAILABLE, and MESSAGE fields in its output.
• The oc get central -o wide command must also include these new fields.
• The VERSION field must accurately reflect the version of the deployed Central component.
• The ADMINPASSWORD field must accurately display the name of the secret containing the admin password.
• The PROGRESSING field must accurately show True when changes are being rolled out and False otherwise.
• The AVAILABLE field must accurately show True when the Central instance is available and False otherwise.
• The MESSAGE field must provide a relevant, human-readable summary of the Central's status.
• The implementation must not negatively impact the performance of the oc get command.
• The new fields must be properly aligned and formatted within the oc get table output.
• The changes must be maintainable and scalable for future additions to the Central CR status.