Bug 2222269 - RFE: Create new section on Settings/Cluster tab for admin settings
Summary: RFE: Create new section on Settings/Cluster tab for admin settings
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Tal Nisan
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-12 13:50 UTC by Avital Pinnick
Modified: 2023-08-02 03:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-02 03:27:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Settings > Cluster tab (36.66 KB, image/png)
2023-07-12 13:50 UTC, Avital Pinnick 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-30893 0 None None None 2023-07-12 13:53:12 UTC

Description Avital Pinnick 2023-07-12 13:50:51 UTC 
Created attachment 1975377 [details]
Settings > Cluster tab

Overview > Settings > Cluster tab.

Currently, enabling the creation of LoadBalancer services is in its own "LoadBalancer" section. This means that an "accordion" is used for a single feature, which seems like a waste of space because it can only hold a single setting.

Also, "Enable Kubevirt proxy" is in the "Preview features" section, although it is not a preview feature.

I suggest that you create a new section called "Cluster administration settings" or "Administration settings" on this tab and use it as a container for settings that are not "Preview features". Both "Enable LoadBalancer" and "Enable KubeVirt proxy" could be placed in this section. It might be useful for enabling tuning parameters if they are exposed in the UI.

The label of the "Enable KubeVirt proxy" checkbox could be rewritten so that it is a bit more informative. Or else you could add a tooltip saying that the feature is enabled by default and improves performance in large-scale pod deployments.
Comment 1 Guohua Ouyang 2023-08-02 03:27:37 UTC 
Close the bug as the jira issue is closed.
Note You need to log in before you can comment on or make changes to this bug.