This is an automated email from the ASF dual-hosted git repository.

gongchao pushed a commit to branch helm-chart
in repository https://gitbox.apache.org/repos/asf/hertzbeat-helm-chart.git

commit bc1de1ee7015378b86c761f1ef07286f70b215ab
Author: tomsun28 <[email protected]>
AuthorDate: Mon Sep 25 16:48:12 2023 +0800

    [hertzbeat] release hertzbeat version v1.4.1 (#1261)
---
 hertzbeat/Chart.yaml                         | 4 ++--
 hertzbeat/templates/collector/configmap.yaml | 1 +
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/hertzbeat/Chart.yaml b/hertzbeat/Chart.yaml
index 32658db..5db886f 100644
--- a/hertzbeat/Chart.yaml
+++ b/hertzbeat/Chart.yaml
@@ -13,9 +13,9 @@ icon: 
https://raw.githubusercontent.com/dromara/hertzbeat/master/home/static/img
 # This is the chart version. This version number should be incremented each 
time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.4.0
+version: 1.4.1
 # This is the version number of the application being deployed. This version 
number should be
 # incremented each time you make changes to the application. Versions are not 
expected to
 # follow Semantic Versioning. They should reflect the version the application 
is using.
 # It is recommended to use it with quotes.
-appVersion: "v1.4.0"
+appVersion: "v1.4.1"
diff --git a/hertzbeat/templates/collector/configmap.yaml 
b/hertzbeat/templates/collector/configmap.yaml
index e9d5124..42d20b7 100644
--- a/hertzbeat/templates/collector/configmap.yaml
+++ b/hertzbeat/templates/collector/configmap.yaml
@@ -34,6 +34,7 @@ data:
           netty:
             enabled: true
             identity: ${IDENTITY:}
+            mode: ${MODE:public}
             manager-host: ${MANAGER_HOST:127.0.0.1}
             manager-port: ${MANAGER_PORT:1158}
     


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to