[ 
https://issues.apache.org/jira/browse/KNOX-3008?focusedWorklogId=907082&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-907082
 ]

ASF GitHub Bot logged work on KNOX-3008:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Feb/24 08:38
            Start Date: 27/Feb/24 08:38
    Worklog Time Spent: 10m 
      Work Description: smolnar82 commented on code in PR #842:
URL: https://github.com/apache/knox/pull/842#discussion_r1503837852


##########
gateway-service-metadata/src/main/java/org/apache/knox/gateway/service/metadata/KnoxMetadataResource.java:
##########
@@ -101,6 +103,7 @@ public GeneralProxyInformation getGeneralProxyInformation() 
{
       final ServerInfoService serviceInfoService = 
gatewayServices.getService(ServiceType.SERVER_INFO_SERVICE);
       final String versionInfo = serviceInfoService.getBuildVersion() + " 
(hash=" + serviceInfoService.getBuildHash() + ")";
       proxyInfo.setVersion(versionInfo);
+      proxyInfo.setHostname(Hostname.getHostname());

Review Comment:
   > I wonder how critical is to have the real hostname in cases like this.
   
   In the case of troubleshooting in a real cluster, this can be critical.
   
   I agree, we may revisit the current usage of `InetAddress.getLocalHost()` 
and replace them, if needed, with this new library.
   
   WRT. the CVE concern, I also had that in my mind, but at the end of the day, 
this new dependency does nothing special but delegate the `gethostname` call to 
the OS-native layer using JNA. This is a 1-class dependency, I cannot see any 
reported vulnerabilities so far.
   <img width="1220" alt="Screenshot 2024-02-27 at 9 37 05" 
src="https://github.com/apache/knox/assets/34065904/d4b08953-c677-400c-a77c-19361df82a6a";>
   





Issue Time Tracking
-------------------

    Worklog Id:     (was: 907082)
    Time Spent: 1h  (was: 50m)

> Add a new banner on the top of Knox UIs
> ---------------------------------------
>
>                 Key: KNOX-3008
>                 URL: https://issues.apache.org/jira/browse/KNOX-3008
>             Project: Apache Knox
>          Issue Type: New Feature
>          Components: AdminUI, Homepage, TokenGenerationUI, TokenManagementUI
>    Affects Versions: 2.1.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 2.1.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> I got to know that Hue has a simple, but really cool feature: it can show a 
> [custom HTML banner|https://gethue.com/add-a-top-banner-to-hue/] on the top 
> of the Hue UI. Implementing a similar feature in Knox can help end-users to:
>  # Share a message of the day like hints, tips, or planned outages.
>  # Identify the cluster (e.g. Prod/Test/Dev) in case the URL is not clear 
> enough.
> An additional improvement would be identifying which Knox gateway is in use, 
> in case of HA deployments and if it's behind a load balancer, which can help 
> with troubleshooting. This information fits perfectly into the existing 
> {{General Proxy Information}} section on the Knox home page; we just need to 
> add this new information as a new row in the table.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to