Workaround for webconsole not working with 0.11.0

[tombarron]

Using the 0.11.0 tarball [1] the cluster installs and starts and I can login to it as kubeadmin but the console is not accessible. The documented port-forwarding fails for lack of "router-default" service.

tbarron@ganges crc_libvirt_0.11.0]$ oc get --all-namespaces routes
NAMESPACE           NAME      HOST/PORT                                         PATH   SERVICES   PORT    TERMINATION          WILDCARD
openshift-console   console   console-openshift-console.apps.test1.tt.testing          console    https   reencrypt/Redirect   None

[tbarron@ganges crc_libvirt_0.11.0]$ kubectl -n openshift-ingress port-forward svc/router-default 443
Error from server (NotFound): services "router-default" not found

[tbarron@ganges crc_libvirt_0.11.0]$ oc get services --all-namespaces
NAMESPACE                                    NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                   AGE
default                                      kubernetes                          ClusterIP   172.30.0.1       <none>        443/TCP                   6d
kube-system                                  etcd                                ClusterIP   172.30.61.61     <none>        2379/TCP                  6d
kube-system                                  host-etcd                           ClusterIP   None             <none>        2379/TCP                  6d
kube-system                                  kubelet                             ClusterIP   None             <none>        10250/TCP                 6d
openshift-apiserver-operator                 metrics                             ClusterIP   172.30.71.207    <none>        443/TCP                   6d
openshift-apiserver                          api                                 ClusterIP   172.30.32.232    <none>        443/TCP                   6d
openshift-cloud-credential-operator          controller-manager-service          ClusterIP   172.30.48.247    <none>        443/TCP                   6d
openshift-cluster-version                    cluster-version-operator            ClusterIP   172.30.50.106    <none>        9099/TCP                  6d
openshift-console                            console                             ClusterIP   172.30.91.89     <none>        443/TCP                   6d
openshift-controller-manager-operator        metrics                             ClusterIP   172.30.130.130   <none>        443/TCP                   6d
openshift-controller-manager                 controller-manager                  ClusterIP   172.30.114.23    <none>        443/TCP                   6d
openshift-dns                                dns-default                         ClusterIP   172.30.0.10      <none>        53/UDP,53/TCP             6d
openshift-image-registry                     image-registry                      ClusterIP   172.30.34.219    <none>        5000/TCP                  6d
openshift-ingress                            router-internal-default             ClusterIP   172.30.166.138   <none>        80/TCP,443/TCP,1936/TCP   6d
openshift-kube-apiserver-operator            metrics                             ClusterIP   172.30.234.171   <none>        443/TCP                   6d
openshift-kube-apiserver                     apiserver                           ClusterIP   172.30.30.222    <none>        443/TCP                  

[1] https://drive.google.com/file/d/15xLBAvmoMSAGB5JeD5mY5vRfk53GcfK5/view?usp=sharing

[tombarron]

As gbraad explained on freenode:#codeready the proper workaround now is to forward router-internal-default instead of router-default.

kubectl -n openshift-ingress port-forward svc/router-internal-default 443 works.

[LalatenduMohanty]

Resolved via https://github.com/code-ready/osp4/commit/0d760632eca8c6e6cc3baf0d309edaa3a46d8c4f