Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not able to view cluster resources after logging in the UI

See original GitHub issue

Description

Two issues

The manifests for deployment to the cluster is wrong - it should be -plugins-dir instead of -plugin-dir
After login to the UI after creating the ingress not able to see any data from the cluster (logged in via SA token the default one) Impact

[ 1 sentence detailing the impact this bug is creating for you ]

Environment and steps to reproduce

Set-up: a managed k3s cluster on Civo (civo.com)
Task: first edit the deployment and change the plugin-dir to plugins-dir
Action(s): after opening the UI , providing the default SA token for authentication I am not able to view anything inside the cluster
Error:

Expected behavior Should be able to see the cluster resources

Issue Analytics

State:
Created 3 years ago
Comments:12 (7 by maintainers)

Top GitHub Comments

1reaction

joaquimrochacommented, Nov 17, 2020

Hi @saiyam1814 . Apparently I failed to be clear about the importance of RBAC in Headlamp. Headlamp checks RBACs for any used Service Account should have a role bound with the desired permissions.

I will update the docs.

0reactions

joaquimrochacommented, Jun 28, 2021

I am closing this due to inactivity. I believe that we have fixed the issues we were having with this effect. Please reopen if it’s still happening with the latest versions.

Top Results From Across the Web

Resolve the Kubernetes object access error in Amazon EKS

1. To find the cluster creator or admin role with primary permissions to configure your cluster, search for the CreateCluster API call in...

Cluster Service Stops Responding - Windows Server

Before you resume a paused cluster node, you must first determine if a cluster node is paused. Click Start, click Run, type cmd...

Initial job has not accepted any resources; check your cluster ...

The error indicates that you cluster has insufficient resources for current job.Since you have not started the slaves i.e worker .

SLEHA 15 SP1 | Administration Guide | Troubleshooting

To make sure the mcastport is not blocked by the firewall, check the firewall settings on each node. Are Pacemaker and Corosync started...

Chapter 8. Getting started with the pcsd Web UI

Configuring advanced cluster configuration options with the pcsd Web UI; 8.3.2. ... Configuring startup order for resource dependencies not managed by ...