[RHOCP 4] Console Pod Throwing 403 Error for Kubernetes Service URL

Solution In Progress - Updated -

Issue

  • Console pods are running, and the cluster console is also accessible. However, while checking the console pod logs, the following error is displayed:
2024-xx-xxTxx:xx:xx.xxxx 2024/xx/xx xx:xx:xx Failed to dial backend: 'websocket: bad handshake' Status: '403 Forbidden' URL: 'https://kubernetes.default.svc/api/v1/namespaces/openshift-console-user-settings/configmaps?watch=true&fieldSelector=metadata.name%3Duser-settings-kubeadmin&cluster=local-cluster'
2024-xx-xxTxx:xx:xx.xxxx 2024/xx/xx xx:xx:xx Failed to dial backend: 'websocket: bad handshake' Status: '403 Forbidden' URL: 'https://kubernetes.default.svc/api/v1/namespaces/openshift-console-user-settings/configmaps?watch=true&fieldSelector=metadata.name%3Duser-settings-kubeadmin&cluster=local-cluster'

Environment

  • Red Hat OpenShift Container Platform
    • 4.14+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content