1. Proposed title of this feature request

Dynamic oc get hc Output: Surface Custom Kubeconfig in Printer Columns

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

The request is to update the HostedCluster (HC) Custom Resource Definition (CRD) AdditionalPrinterColumns or the HyperShift Operator’s status reconciliation logic.

Currently, the KUBECONFIG column in the oc get hc output is statically mapped to the internal/default admin kubeconfig secret (.status.kubeconfig.name). When a user configures a custom DNS via spec.kubeAPIServerDNSName, a secondary, functional kubeconfig is generated (.status.customKubeconfig.name).

This RFE proposes that the CLI output should dynamically reflect this custom secret name, either by replacing the default value in the KUBECONFIG column or by adding a dedicated CUSTOM-KUBECONFIG column.

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

• Reduced Operational Complexity: Administrators managing multiple HostedClusters currently have to run oc get hc <name> -o yaml and manually grep for the customKubeconfig field. This is a repetitive, manual task that should be surfaced at a glance.

• Prevention of Configuration Errors: The current output is misleading. It shows the internal hosted-admin-kubeconfig as the primary access point. If an admin uses this by mistake on a restricted network (where only the custom DNS/Port is reachable), they face connectivity timeouts, leading to unnecessary troubleshooting cycles.

• Improved Visibility for Automation: CI/CD pipelines and wrapper scripts often rely on the default oc get output to identify resources. Surfacing the "correct" usable kubeconfig for the defined environment ensures automation tools pick up the intended access secret.

• Feature Completeness: Since HyperShift supports custom KAS DNS as a first-class feature, the CLI experience should reflect that configuration state

4. List any affected packages or components.

HCP