Open johncowen opened 9 months ago
my use-case is in Kong Education labs. Not having that on all the pages in Mesh UI would certainly help with not distracting learners and creating questions for instructors.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Description
The GUI provides an update check to see if there are any newer Kuma versions available than the one you are running.
This is fine if the person using the GUI is the person responsible for upgrading Kuma, but there are instances where the person using the GUI and seeing the upgrade prompt is not responsible for upgrading Kuma, two I can think of off the top of my head:
In these case it might be good to add some sort of flag to the Kuma binary to enable operators to turn off this GUI check. If the people using the GUI have no way to act on the prompt then the prompt could be distracting. We could then pass this flag/config through via the GUIs
index.html
environment variables.As a side note, I'm not totally sure if there is anything in the backend logs (and therefore accessible/visible only to operators) that notifies of an available upgrade?