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

Option to Disable Secret Values in Kubernees Dashboard UI #9340

Open
mikeNetHopper opened this issue Aug 5, 2024 · 3 comments
Open

Option to Disable Secret Values in Kubernees Dashboard UI #9340

mikeNetHopper opened this issue Aug 5, 2024 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@mikeNetHopper
Copy link

What would you like to be added?

I would love the ability to leave out the value of secrets or asterisk them out when viewing secrets in the kubernetes dashboard ui. Seems like it could be a relatively easy addition just not feeding the values to the UI.

Why is this needed?

It allows for increased security in clusters and peace of mind that ever changing resource additions/subtractions/types don't need to always need to be managed/accounted for with ultra specific RBAC.

@mikeNetHopper mikeNetHopper added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 5, 2024
@floreks
Copy link
Member

floreks commented Aug 9, 2024

Force hiding secret values only on the UI side wouldn't increase security since it would be just a workaround. API would still send full response and it would be as easy as checking the networking tab to see it. The only proper way of managing that is through Kubernetes native features such as RBACs. Dashboard is basically just a proxy to the K8S API server.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 7, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

4 participants