Bug: Running in-cluster and the items in Workloads tab has wrong order since 4.19

[ludd98]

When running conosle in-cluster on vanilla k8s the tab Workloads have the wrong order. Topology, Pods and Deployments drops to the bottom, they should be on the top. Before 4.19 this bug in not there. Booting up same manifest config with 4.18 image the ordering is correct, from 4.19 and newer the order is wrong.

I dont have enough skills in TypeScript to debug where in the code it goes wrong.

My settings is like this:

      containers:
        - name: console
          image: quay.io/openshift/origin-console:4.22
          ports:
            - containerPort: 9000
          env:
            - name: BRIDGE_K8S_AUTH_BEARER_TOKEN
              valueFrom:
                secretKeyRef:
                  name: openshift-console-token
                  key: token
          args:
            - "/opt/bridge/bin/bridge"
            - "--k8s-mode=in-cluster"
            - "--k8s-auth=bearer-token"
            - "--user-auth=disabled"
            - "--user-settings-location=localstorage"
            - "--public-dir=/opt/bridge/static"

From image tag 4.19 and newser the (wrong) order is like this, Topology, Pods, Deployments should have the order 1, 2, 3 in Workloads list, but does not when running with in.cluster on vanilla k8s for some reason.

Workloads
StatefulSets
Secrets
ConfigMaps

CronJobs
Jobs
DaemonSets
ReplicaSets
ReplicationControllers
HorizontalPodAutoscalers
PodDisruptionBudgets
Topology
Pods
Deployments

If I boot up 4.18 the order is correct,

Pods
Deployments
StatefulSets
Secrets
ConfigMaps
CronJobs
Jobs
DaemonSets
ReplicaSets
ReplicationControllers
HorizontalPodAutoscalers
PodDisruptionBudgets

I have tested these images, all have the wrong ordering

image: quay.io/openshift/origin-console:4.22
image: quay.io/openshift/origin-console:4.19
image: quay.io/openshift/origin-console:latest

Image 4.18 have correct ordering
image: quay.io/openshift/origin-console:4.18