Chapter 1. HawtIO release notes HawtIO 4.1 / HawtIO-Online 2.1
Chapter 1. HawtIO release notes HawtIO 4.1 / HawtIO-Online 2.1 This chapter provides release information about HawtIO Diagnostic Console Guide. 1.1. HawtIO Features The HawtIO Diagnostic Console includes the following main features: Runtime management of JVM via JMX, especially that of Camel applications with specialised views Visualisation and debugging/tracing of Camel routes Simple managing and monitoring of application metrics 1.2. Release features HawtIO UI PatternFly upgraded to v5 HawtIO Operator Support for s390x and ppc64le architectures; Addition of default text for console launcher in OpenShift dashboard HawtIO Online Upgrade of container web server to nginx 1.22.1 Replacement of nginx njs module with separate gateway container Gateway container acts as side-car to main application container, running Express 4.21.0 Node-js application server Gateway is responsible for the following functions: Limit access to OpenShift cluster interfaces Manage connection requests to jolokia interfaces on applicable OpenShift pods Upgrade of UI components to Patternfly 5 Discovery: Separate pods by namespace into their own tabs Limit the display of pods from each namespace to a default number (3) Adds pagination for navigating to the set of applicable pods in a namespace Option to modify the number of pods displayed per namespace Option to modify the polling interval between checks on pod jolokia interfaces Discover plugin only displayed if no connection to a pod has yet been requested Support for IBM Power and IBM Z This release of Red Hat build of HawtIO adds support for IBM Power and IBM Z. 1.3. HawtIO known issues The following issue remain with HawtIO for this release: HAWNG-767 Cannot inject custom icons as Application Menu entry The imageRelativePath property must be relative to the route host hence is currently limited as to what icons can be used (the poweredby icon is a Red Hat branded image). Need a way to inject such icons into the path, maybe via including them in a configmap (another one??) or including them directly in the CR using base64 (CSVs do it). Revised on 2024-12-12 11:05:02 UTC