[#531] Update to Hono 2.5.1.

charts/hono/Chart.yaml

@@ -15,9 +15,9 @@ name: hono
 description: |
   Eclipse Hono™ provides remote service interfaces for connecting large numbers of IoT devices to a back end and
   interacting with them in a uniform way regardless of the device communication protocol.
-version: 2.6.0
+version: 2.6.1
 # Version of Hono being deployed by the chart
-appVersion: 2.5.0
+appVersion: 2.5.1
 keywords:
 - iot-chart
 - IoT

charts/hono/README.md

@@ -101,6 +101,11 @@ The command removes all the Kubernetes components associated with the chart and
 
 ## Release Notes
 
+### 2.6.1
+
+* Use Hono 2.5.1 container images.
+* Update jaegertracing/all-in-one and opentelemetry-collector image versions.
+
 ### 2.6.0
 
 * Use Hono 2.5.0 container images.
@@ -422,7 +427,7 @@ The parameters enable the deployment of a simple AMQP 1.0 based messaging infras
 broker and configure adapters and services to use AMQP 1.0 based messaging.
 
 To use the service type `NodePort` instead of `LoadBalancer`, the following parameters must be added:
-`--set useLoadBalancer=false --set kafka.externalAccess.service.type=NodePort`.
+`--set useLoadBalancer=false --set kafka.externalAccess.broker.service.type=NodePort --set kafka.externalAccess.controller.service.type=NodePort`.
 
 ### Integrating with an existing AMQP Messaging Network
 
@@ -666,10 +671,6 @@ The Helm chart can be configured to use these *native* images by means of explic
 name as described in *Using specific Container Images*. The names of the images based on native executables are the
 standard image names appended by `-native`.
 
-The native executables used in the images currently do not properly detect the memory and CPU resource limits defined on the
-container. This is due to a bug in the native-image builder in GraalVM versions before 22.1. Future versions of Hono will
-probably not be affected by this anymore.
-
 In order to make the native executables aware of the memory limits, the
 [`-Xmx` GraalVM parameter](https://www.graalvm.org/22.0/reference-manual/native-image/MemoryManagement/#java-heap-size) can
 be passed to the native executable as a command line parameter. This can be done by setting the `cmdLineArgs` property of the

charts/hono/values.yaml

@@ -2053,7 +2053,7 @@ jaegerBackendExample:
   enabled: false
   # allInOneImage contains the name (including tag)
   # of the container image to use for the example Jaeger back end.
-  allInOneImage: "jaegertracing/all-in-one:1.50"
+  allInOneImage: "jaegertracing/all-in-one:1.57"
   # [DEPRECATED: use probes instead] livenessProbeInitialDelaySeconds contains the value to use for the "initialDelaySeconds"
   # configuration property of the component's liveness probe.
   # The value of the top level "livenessProbeInitialDelaySeconds" property will be used if not set.
@@ -2122,7 +2122,7 @@ jaegerBackendExample:
 # to use for the OpenTelemetry collector agent sidecar containers.
 # These containers are deployed with Hono's components if the example Jaeger all-in-one
 # deployment is disabled and "otelCollectorAgentConfigMap" is not null.
-otelCollectorAgentImage: "otel/opentelemetry-collector:0.86.0"
+otelCollectorAgentImage: "otel/opentelemetry-collector:0.100.0"
 # otelCollectorAgentConfigMap can be used to specify the name of an existing ConfigMap
 # from which an OpenTelemetry collector configuration should be read.
 # If a ConfigMap name is given, an OpenTelemetry collector agent sidecar container will