Currently, in order to access a RHOV spoke using oc client, we manually created Route on the hub. This maps an FQDN (e.g., api.clc-kv.apps.mist06-0.qe.red-chesterfield.com) to the spoke's API server service.

However, from my understanding, a Route is designed to be accessed externally via the hub's Ingress Controller, which listens on standard ports (typically 80 for HTTP and 443 for HTTPS) hence, client connections using this method target port 443.

Example-

ashafi@ashafi-mac automation % oc login --token=sha256~VC_xxx-xxx--server=https://api.clc-kv-3.apps.mist12-0.qe.red-chesterfield.com:443 --insecure-skip-tls-verify=true

WARNING: Using insecure TLS client config. Setting this option is not supported!

Logged into "https://api.clc-kv-3.apps.mist12-0.qe.red-chesterfield.com:443" as "kube:admin" using the token provided.

You have access to 65 projects, the list has been suppressed. You can list all projects with 'oc projects'

Using project "default". 

Since existing automation base uses port 6443 to log in, we need to find a soln to enable that. So the primary goal is to enable oc login --server=https://<spoke-api-fqdn>:6443 --insecure-skip-tls-verify=true to successfully configure the client's oc environment for subsequent direct commands to the spoke.