This bug is a backport clone of [Bugzilla Bug 2111686](https://bugzilla.redhat.com/show_bug.cgi?id=2111686). The following is the description of the original bug:
—
Description of problem:
While using the console web UI with a nanokube cluster at our hack week in June 2022, we found different NPEs when the project or build status wasn't set.

Version-Release number of selected component (if applicable):
4.12 (but maybe all)

How reproducible:
Always, but only when running a nanokube cluster

Steps to Reproduce:
1. Clone and build https://github.com/RedHatInsights/nanokube

export KUBEBUILDER_ASSETS=`~/go/bin/setup-envtest use 1.21 -p path`
./nanokube

2. Run our console web UI against this cluster!

1. do not call ./contrib/oc-environment.sh !!
   export BRIDGE_USER_AUTH="disabled"
   export BRIDGE_K8S_MODE="off-cluster"
   export BRIDGE_K8S_MODE_OFF_CLUSTER_ENDPOINT="http://127.0.0.1:8090/"
   export BRIDGE_K8S_AUTH="bearer-token"
   export BRIDGE_K8S_AUTH_BEARER_TOKEN="ignored-by-proxy"
   ./bin/bridge

Actual results:
Crashes while navigate to the project list or details page.
Crash on the build config list page.

Expected results:
No crashes, or at least not the described.

Additional info: