Bug 2221942 - Help user find where to enable LoadBalancer service for SSH access
Summary: Help user find where to enable LoadBalancer service for SSH access
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
high
Target Milestone: ---
: 4.14.0
Assignee: Tal Nisan
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-11 10:55 UTC by Avital Pinnick
Modified: 2023-08-08 11:24 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-08 11:24:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
LoadBalancer service disabled with no explanation (21.58 KB, image/png)
2023-07-11 10:55 UTC, Avital Pinnick 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-31544 0 None None None 2023-07-31 09:05:37 UTC

Description Avital Pinnick 2023-07-11 10:55:21 UTC 
Created attachment 1975130 [details]
LoadBalancer service disabled with no explanation

In 4.13, the user could go to VM details > Details tab and select a `LoadBalancer` service from the "SSH service type" list for SSH access to a VM. 

In 4.14, the user has to go to Overview > Settings > Cluster > LoadBalancer section to enable the creation of `LoadBalancer` services before a `LoadBalancer` service can be selected. The LoadBalancer service option is disabled for the VM with no explanation.

I recommend adding a tooltip to the "SSH service type" list saying that the Cluster setting has to be enabled before a LoadBalancer service can be created.
Comment 2 Avital Pinnick 2023-08-08 11:24:10 UTC 
Based on discussion and reorganization of the networking documentation, we agreed that there is no need to make UI changes. Closing this bug.
Note You need to log in before you can comment on or make changes to this bug.