Replies: 7 comments 2 replies
-
|
I'm open to adding this new field to the first run dialog, but it doesn't look like the right place. Our goal with the first run dialog is to keep it as lean as possible so that a user can accept the defaults and start working with Rancher Desktop without any friction. This could fit under preferences, perhaps under Virtual Machine => Network? Some questions that come to mind while thinking about adding this to the first run dialog:
|
Beta Was this translation helpful? Give feedback.
-
I just talked with @Nino-K about it (and looked at #3093), and this is actually a Kubernetes and not a VM setting. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not seeing any instances of a masked input for IP addresses in Rancher Dashboard. This might be a good enhancement for |
Beta Was this translation helpful? Give feedback.
-
It is my understanding that in this particular use-case the valid entries are limited to If this is the case, then a dropdown list seems more appropriate than a generic IP address input widget. |
Beta Was this translation helpful? Give feedback.
-
I agree with this. Additional, the description is written from our point of view; we don't expect the user to know what the "Guest agent service listener" is, so why should they care about the bind address? Can we find a description that explains what difference it makes to them? Maybe it needs to go into a tooltip? |
Beta Was this translation helpful? Give feedback.
-
|
In addition to what is mentioned above, why the first dialog box may not be a suitable place for this is, users would have to perform a factory reset and this config change should not require a factory reset. Maybe just restarting Rancher Desktop would be adequate since that also restarts Also, another option to incorporate this configuration is via provisioning script. This needs to be backed by documentation where we elaborate on what it does and what are the available values for the property to avoid user misconfiguration. |
Beta Was this translation helpful? Give feedback.
-
All settings from the first-run dialog are changeable via the regular Preferences dialog as well, so that would not be an issue. But as @rak-phillip already mentioned, the first-run dialog should only prompt for essential settings that virtually every user wants to setup correctly from the start, and that's why this option doesn't qualify. To start with, it is still not clear to me what exactly it is that it configures. 😄 |
Beta Was this translation helpful? Give feedback.
-
|
Just going to attach the original issue here: #3093 |
Beta Was this translation helpful? Give feedback.
-
|
We agreed on integrating the setting as a CLI command and not as part of the UI for now: #3940 |
Beta Was this translation helpful? Give feedback.
-
Problem Description
rancher-sandbox/rancher-desktop-agent#27 adds a service listener address as an input parameter to the guest agent. It would be nice to reflect the change somewhere in the UI.
Proposed Solution
I'm not yet sure how the solution should look like. I think the input field could be either part of the first run window or the preferences page. Because I assume the config needs to be rewritten and the service to be restarted, I thought the first run window would be a good idea, e.g.:
But there might be reasons for other places I currently don't see.
Also, I was wondering which type of input field to use. At first I thought about adding an IP-address field, e.g.: https://www.npmjs.com/package/vue-ip . But then I noticed the Rancher UI DevKit https://rancher.github.io/dashboard/ doesn't mention an IP address field add all. So I assumed to better stick with an usual Labeled-Input field.
Additional Information
No response
Beta Was this translation helpful? Give feedback.
All reactions