Bug 2222269

Summary: RFE: Create new section on Settings/Cluster tab for admin settings
Product: Container Native Virtualization (CNV) Reporter: Avital Pinnick <apinnick>
Component: User ExperienceAssignee: Tal Nisan <tnisan>
Status: CLOSED NOTABUG QA Contact: Guohua Ouyang <gouyang>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.14.0CC: gouyang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-02 03:27:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Settings > Cluster tab none

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.