Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Action] Set up access to the cluster through the K8s dashboard #19

Closed
AntonioDiTuri opened this issue Jan 9, 2024 · 4 comments
Closed

Comments

@AntonioDiTuri
Copy link
Contributor

AntonioDiTuri commented Jan 9, 2024

Depends on/blocked by #18

The current monitoring deployments lacks a user-friendly graphical interface.

This issue is about implementing a Kubernetes dashboard to simplify resource visualization and management.

Here there is a guide on how to set up the k8s Dashboard.

It is not specified what permissions the service account because in the user creation example the official dashboard repo provides an example using admin role which we don't want to use because it would lead to security issues.

You can start from the one created in this issue.

If additional permissions are needed you can create a new role called user-dashboard.

@nikimanoledaki nikimanoledaki changed the title Set up access to the cluster through the K8s dashboard [Action] Set up access to the cluster through the K8s dashboard Jan 9, 2024
@dipankardas011
Copy link
Contributor

[Updates] #18 is merged!
@AntonioDiTuri

@nikimanoledaki
Copy link
Contributor

nikimanoledaki commented Feb 20, 2024

We've opted for a public Grafana instance that can provision custom-made Grafana dashboards. I'm not sure that we need the k8s dashboard since it is a general solution that isn't tailored to our needs. I vote for closing this since it's kind of a duplicate. WDYT @AntonioDiTuri?

@rossf7
Copy link
Contributor

rossf7 commented Feb 21, 2024

I think this is still useful to make contributing easier. The public Grafana + Flux manifests help but it can still be useful to be able to see the cluster state.

Could we keep this but defer it till after KubeCon?

@leonardpahlke
Copy link
Member

Could we keep this but defer it till after KubeCon?

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants