kubermatic / kubermatic/dashboard

Hiding settings from UI that are disabled by admin

Open
#5,603 3 comments 0 reactions 0 assignees View on GitHub
customer-request kind/feature priority/low sig/api sig/ui
Dominant language
Go
Stars
50
Forks
73
Avg merge
2d 22h
Merged PRs (30d)
31

Description

### Description of the feature you would like to add / User story

As a KKP admin
I would like to hide settings like User Cluster Logging and others when they are disabled
in order to cause less confusion for KKP users

### Solution details

- When Enable by Default **is not** checked AND Enforce Default **is** checked in the Defaults pane on the Admin UI, thes setting for the user will be greyed out, but still can be seen. The idea is that in this case instead of greying out the feature, it should just not appear at all to cause less confusion.

### Alternative approaches

- Don't paying attention to inactive, greyed out features

### Use cases

- When a KKP installation is used by several different customers, they can see if features are greyed out and being inactive, but still could be available, which causes overwhelm for the support

### Additional information

Contributor guide

Open the contributing guide

Research direction

Start at the Admin UI Defaults pane and trace how settings are rendered for users. Confirm the Enable by Default and Enforce Default combination, then verify that affected settings are absent rather than greyed out while other settings remain visible.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.