Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8393

RFE: Display RHACS Central URL and Admin Credentials in the OpenShift Console Post-Deployment

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • rhacs-4.10.0, rhacs-4.12.0
    • rhacs-ui
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request
      Display RHACS Central URL and Admin Credentials in the OpenShift Console Post-Deployment

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

      This is a *UI/UX enhancement request* for the Red Hat Advanced Cluster Security (RHACS) Operator on OpenShift.

      When an administrator deploys a new RHACS Central instance using the Operator, the deployment is considered "complete" from the console's perspective, but the two most critical pieces of information needed to access the application are not shown:

      1.  *The Central Console URL*
      2.  *The initial `admin` password*

      To get this information, the administrator must leave the OpenShift Web Console's "Installed Operators" page and perform manual, CLI-based actions:

      • To find the URL, they must run `oc get route central -n stackrox ...` or manually navigate to the *Networking* > *Routes* section.
      • To find the password, they must run `oc get secret central-htpasswd -n stackrox ...` and decode the value.

      This request is to have the RHACS Operator automatically populate these two values directly into the OpenShift Console, specifically on the details page for the `Central` Custom Resource instance.

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

      Improve "Day 1" User Experience: The current workflow is disjointed and requires switching between the web UI and a command-line interface. A successful UI-based installation should be followed by UI-based access.

      Reduce Time-to-Value: This feature would eliminate the manual steps of searching for routes and decoding secrets, allowing administrators to log in to RHACS immediately after deployment.

      Establish Product Consistency: Other Red Hat products, such as *Red Hat Advanced Cluster Management (ACM)*, already provide this superior experience. When deploying a Hosted Control Plane (HCP) cluster, the ACM console clearly displays the cluster's API address, console URL, and initial `kubeadmin` credentials on the same page. RHACS should align with this user-friendly standard.

      Lower the Barrier to Entry: Requiring `oc` CLI-fu to simply log in for the first time creates unnecessary friction for users who are less comfortable with the command line (e.g., new users, security auditors, or managers) and prefer to operate from the OpenShift Web Console.

      4. List any affected packages or components.
      RHACS-UI

              masyed@redhat.com Mansur Syed
              rhn-support-dpateriy Divyam Pateriya
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None