From 3d06c03c41f2207c2d98154888e3bd2f90e04690 Mon Sep 17 00:00:00 2001 From: TrueCharts-Bot Date: Sun, 20 Mar 2022 21:52:14 +0000 Subject: [PATCH] Commit new App releases for TrueCharts Signed-off-by: TrueCharts-Bot --- stable/zigbee2mqtt/2.0.7/helm-values.md | 34 ------ stable/zigbee2mqtt/2.0.7/ix_values.yaml | 37 ------- .../zigbee2mqtt/{2.0.7 => 2.0.8}/CHANGELOG.md | 18 ++-- stable/zigbee2mqtt/{2.0.7 => 2.0.8}/CONFIG.md | 0 .../zigbee2mqtt/{2.0.7 => 2.0.8}/Chart.lock | 2 +- .../zigbee2mqtt/{2.0.7 => 2.0.8}/Chart.yaml | 2 +- stable/zigbee2mqtt/{2.0.7 => 2.0.8}/README.md | 0 .../zigbee2mqtt/{2.0.7 => 2.0.8}/SKIPINSTALL | 0 .../{2.0.7 => 2.0.8}/app-readme.md | 0 .../{2.0.7 => 2.0.8}/charts/common-9.1.6.tgz | Bin stable/zigbee2mqtt/2.0.8/helm-values.md | 61 +++++++++++ stable/zigbee2mqtt/2.0.8/ix_values.yaml | 101 ++++++++++++++++++ .../{2.0.7 => 2.0.8}/questions.yaml | 4 +- .../zigbee2mqtt/{2.0.7 => 2.0.8}/security.md | 14 +++ .../{2.0.7 => 2.0.8}/templates/common.yaml | 0 .../zigbee2mqtt/{2.0.7 => 2.0.8}/values.yaml | 0 16 files changed, 189 insertions(+), 84 deletions(-) delete mode 100644 stable/zigbee2mqtt/2.0.7/helm-values.md delete mode 100644 stable/zigbee2mqtt/2.0.7/ix_values.yaml rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/CHANGELOG.md (91%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/CONFIG.md (100%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/Chart.lock (78%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/Chart.yaml (97%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/README.md (100%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/SKIPINSTALL (100%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/app-readme.md (100%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/charts/common-9.1.6.tgz (100%) create mode 100644 stable/zigbee2mqtt/2.0.8/helm-values.md create mode 100644 stable/zigbee2mqtt/2.0.8/ix_values.yaml rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/questions.yaml (99%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/security.md (91%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/templates/common.yaml (100%) rename stable/zigbee2mqtt/{2.0.7 => 2.0.8}/values.yaml (100%) diff --git a/stable/zigbee2mqtt/2.0.7/helm-values.md b/stable/zigbee2mqtt/2.0.7/helm-values.md deleted file mode 100644 index 1b3d6b8a4d6..00000000000 --- a/stable/zigbee2mqtt/2.0.7/helm-values.md +++ /dev/null @@ -1,34 +0,0 @@ -# Default Helm-Values - -TrueCharts is primarily build to supply TrueNAS SCALE Apps. -However, we also supply all Apps as standard Helm-Charts. In this document we aim to document the default values in our values.yaml file. - -Most of our Apps also consume our "common" Helm Chart. -If this is the case, this means that all values.yaml values are set to the common chart values.yaml by default. This values.yaml file will only contain values that deviate from the common chart. -You will, however, be able to use all values referenced in the common chart here, besides the values listed in this document. - -## Values - -| Key | Type | Default | Description | -|-----|------|---------|-------------| -| env.ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API | bool | `true` | | -| env.ZIGBEE2MQTT_CONFIG_FRONTEND_PORT | string | `"{{ .Values.service.main.ports.main.port }}"` | | -| env.ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC | string | `"zigbee2mqtt"` | | -| env.ZIGBEE2MQTT_CONFIG_MQTT_SERVER | string | `"mqtt://localhost"` | | -| env.ZIGBEE2MQTT_CONFIG_PERMIT_JOIN | bool | `true` | | -| env.ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER | string | `"auto"` | | -| env.ZIGBEE2MQTT_CONFIG_SERIAL_PORT | string | `"/dev/ttyUSB0"` | | -| env.ZIGBEE2MQTT_DATA | string | `"/data"` | | -| image.pullPolicy | string | `"IfNotPresent"` | | -| image.repository | string | `"tccr.io/truecharts/zigbee2mqtt"` | | -| image.tag | string | `"v1.24.0@sha256:2574cbd6af36d0305c8034804e2c64f672757133d71b14f87f36913a9b97e754"` | | -| persistence.data.enabled | bool | `true` | | -| persistence.data.mountPath | string | `"/data"` | | -| podSecurityContext.runAsGroup | int | `0` | | -| podSecurityContext.runAsUser | int | `0` | | -| secret.ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD | string | `""` | | -| secret.ZIGBEE2MQTT_CONFIG_MQTT_USER | string | `""` | | -| securityContext.runAsNonRoot | bool | `false` | | -| service.main.ports.main.port | int | `10103` | | - -All Rights Reserved - The TrueCharts Project diff --git a/stable/zigbee2mqtt/2.0.7/ix_values.yaml b/stable/zigbee2mqtt/2.0.7/ix_values.yaml deleted file mode 100644 index 89402e701ab..00000000000 --- a/stable/zigbee2mqtt/2.0.7/ix_values.yaml +++ /dev/null @@ -1,37 +0,0 @@ -image: - repository: tccr.io/truecharts/zigbee2mqtt - tag: v1.24.0@sha256:2574cbd6af36d0305c8034804e2c64f672757133d71b14f87f36913a9b97e754 - pullPolicy: IfNotPresent - -secret: - ZIGBEE2MQTT_CONFIG_MQTT_USER: "" - ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD: "" - -env: - ZIGBEE2MQTT_DATA: "/data" - ZIGBEE2MQTT_CONFIG_FRONTEND_PORT: "{{ .Values.service.main.ports.main.port }}" - ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API: true - # User defined - ZIGBEE2MQTT_CONFIG_PERMIT_JOIN: true - ZIGBEE2MQTT_CONFIG_MQTT_SERVER: "mqtt://localhost" - ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC: "zigbee2mqtt" - ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyUSB0" - ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "auto" - -securityContext: - runAsNonRoot: false - -podSecurityContext: - runAsUser: 0 - runAsGroup: 0 - -service: - main: - ports: - main: - port: 10103 - -persistence: - data: - enabled: true - mountPath: "/data" diff --git a/stable/zigbee2mqtt/2.0.7/CHANGELOG.md b/stable/zigbee2mqtt/2.0.8/CHANGELOG.md similarity index 91% rename from stable/zigbee2mqtt/2.0.7/CHANGELOG.md rename to stable/zigbee2mqtt/2.0.8/CHANGELOG.md index 9bc4917e42c..a117580e2bf 100644 --- a/stable/zigbee2mqtt/2.0.7/CHANGELOG.md +++ b/stable/zigbee2mqtt/2.0.8/CHANGELOG.md @@ -1,6 +1,15 @@ # Changelog
+ +### [zigbee2mqtt-2.0.8](https://github.com/truecharts/apps/compare/zigbee2mqtt-2.0.7...zigbee2mqtt-2.0.8) (2022-03-20) + +#### Fix + +* create an initial file ([#2233](https://github.com/truecharts/apps/issues/2233)) + + + ### [zigbee2mqtt-2.0.7](https://github.com/truecharts/apps/compare/zigbee2mqtt-2.0.6...zigbee2mqtt-2.0.7) (2022-03-20) @@ -88,12 +97,3 @@ * update helm general non-major helm releases ([#1901](https://github.com/truecharts/apps/issues/1901)) - - -### [zigbee2mqtt-1.0.42](https://github.com/truecharts/apps/compare/zigbee2mqtt-1.0.41...zigbee2mqtt-1.0.42) (2022-02-08) - -#### Chore - -* update helm general non-major helm releases ([#1871](https://github.com/truecharts/apps/issues/1871)) - - diff --git a/stable/zigbee2mqtt/2.0.7/CONFIG.md b/stable/zigbee2mqtt/2.0.8/CONFIG.md similarity index 100% rename from stable/zigbee2mqtt/2.0.7/CONFIG.md rename to stable/zigbee2mqtt/2.0.8/CONFIG.md diff --git a/stable/zigbee2mqtt/2.0.7/Chart.lock b/stable/zigbee2mqtt/2.0.8/Chart.lock similarity index 78% rename from stable/zigbee2mqtt/2.0.7/Chart.lock rename to stable/zigbee2mqtt/2.0.8/Chart.lock index 08f6f0d38f1..d668e00bfb0 100644 --- a/stable/zigbee2mqtt/2.0.7/Chart.lock +++ b/stable/zigbee2mqtt/2.0.8/Chart.lock @@ -3,4 +3,4 @@ dependencies: repository: https://truecharts.org version: 9.1.6 digest: sha256:d65395039794859a54173a3b1687c20877eeb9127fa4044016eb188cc1644675 -generated: "2022-03-20T12:04:50.077032082Z" +generated: "2022-03-20T21:47:23.290059519Z" diff --git a/stable/zigbee2mqtt/2.0.7/Chart.yaml b/stable/zigbee2mqtt/2.0.8/Chart.yaml similarity index 97% rename from stable/zigbee2mqtt/2.0.7/Chart.yaml rename to stable/zigbee2mqtt/2.0.8/Chart.yaml index d095bed81c2..d024fa67de5 100644 --- a/stable/zigbee2mqtt/2.0.7/Chart.yaml +++ b/stable/zigbee2mqtt/2.0.8/Chart.yaml @@ -19,7 +19,7 @@ maintainers: name: zigbee2mqtt sources: - https://github.com/Koenkk/zigbee2mqtt -version: 2.0.7 +version: 2.0.8 annotations: truecharts.org/catagories: | - media diff --git a/stable/zigbee2mqtt/2.0.7/README.md b/stable/zigbee2mqtt/2.0.8/README.md similarity index 100% rename from stable/zigbee2mqtt/2.0.7/README.md rename to stable/zigbee2mqtt/2.0.8/README.md diff --git a/stable/zigbee2mqtt/2.0.7/SKIPINSTALL b/stable/zigbee2mqtt/2.0.8/SKIPINSTALL similarity index 100% rename from stable/zigbee2mqtt/2.0.7/SKIPINSTALL rename to stable/zigbee2mqtt/2.0.8/SKIPINSTALL diff --git a/stable/zigbee2mqtt/2.0.7/app-readme.md b/stable/zigbee2mqtt/2.0.8/app-readme.md similarity index 100% rename from stable/zigbee2mqtt/2.0.7/app-readme.md rename to stable/zigbee2mqtt/2.0.8/app-readme.md diff --git a/stable/zigbee2mqtt/2.0.7/charts/common-9.1.6.tgz b/stable/zigbee2mqtt/2.0.8/charts/common-9.1.6.tgz similarity index 100% rename from stable/zigbee2mqtt/2.0.7/charts/common-9.1.6.tgz rename to stable/zigbee2mqtt/2.0.8/charts/common-9.1.6.tgz diff --git a/stable/zigbee2mqtt/2.0.8/helm-values.md b/stable/zigbee2mqtt/2.0.8/helm-values.md new file mode 100644 index 00000000000..de389c6d1a3 --- /dev/null +++ b/stable/zigbee2mqtt/2.0.8/helm-values.md @@ -0,0 +1,61 @@ +# Default Helm-Values + +TrueCharts is primarily build to supply TrueNAS SCALE Apps. +However, we also supply all Apps as standard Helm-Charts. In this document we aim to document the default values in our values.yaml file. + +Most of our Apps also consume our "common" Helm Chart. +If this is the case, this means that all values.yaml values are set to the common chart values.yaml by default. This values.yaml file will only contain values that deviate from the common chart. +You will, however, be able to use all values referenced in the common chart here, besides the values listed in this document. + +## Values + +| Key | Type | Default | Description | +|-----|------|---------|-------------| +| env.ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API | bool | `true` | | +| env.ZIGBEE2MQTT_CONFIG_FRONTEND_PORT | string | `"{{ .Values.service.main.ports.main.port }}"` | | +| env.ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC | string | `"zigbee2mqtt"` | | +| env.ZIGBEE2MQTT_CONFIG_MQTT_SERVER | string | `"mqtt://localhost"` | | +| env.ZIGBEE2MQTT_CONFIG_PERMIT_JOIN | bool | `true` | | +| env.ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER | string | `"auto"` | | +| env.ZIGBEE2MQTT_CONFIG_SERIAL_PORT | string | `"/dev/ttyUSB0"` | | +| env.ZIGBEE2MQTT_DATA | string | `"/data"` | | +| image.pullPolicy | string | `"IfNotPresent"` | | +| image.repository | string | `"tccr.io/truecharts/zigbee2mqtt"` | | +| image.tag | string | `"v1.24.0@sha256:2574cbd6af36d0305c8034804e2c64f672757133d71b14f87f36913a9b97e754"` | | +| initContainers.init-config.args[0] | string | `"if [ -f /data/configuration.yaml ]; then\n echo \"Initial configuration exists. Skipping\";\nelse\n echo \"Creating initial configuration\";\n touch /data/configuration.yaml;\n echo \"# Configuration bellow will be always be overridden\" >> /data/configuration.yaml;\n echo \"# from environment settings on the Scale Apps UI.\" >> /data/configuration.yaml;\n echo \"# You however will not see this values change in the file.\" >> /data/configuration.yaml;\n echo \"##########################################################\" >> /data/configuration.yaml;\n echo \"experimental:\" >> /data/configuration.yaml;\n echo \" new_api: $ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API\" >> /data/configuration.yaml;\n echo \"frontend:\" >> /data/configuration.yaml;\n echo \" port: $ZIGBEE2MQTT_CONFIG_FRONTEND_PORT\" >> /data/configuration.yaml;\n echo \"permit_join: $ZIGBEE2MQTT_CONFIG_PERMIT_JOIN\" >> /data/configuration.yaml;\n echo \"mqtt:\" >> /data/configuration.yaml;\n echo \" server: $ZIGBEE2MQTT_CONFIG_MQTT_SERVER\" >> /data/configuration.yaml;\n echo \" base_topic: $ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC\" >> /data/configuration.yaml;\n if [ ! -z \"$ZIGBEE2MQTT_CONFIG_MQTT_USER\" ];\n then\n echo \" user: $ZIGBEE2MQTT_CONFIG_MQTT_USER\" >> /data/configuration.yaml;\n fi;\n if [ ! -z \"$ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD\" ];\n then\n echo \" password: $ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD\" >> /data/configuration.yaml;\n fi;\n echo \"serial:\" >> /data/configuration.yaml;\n echo \" port: $ZIGBEE2MQTT_CONFIG_SERIAL_PORT\" >> /data/configuration.yaml;\n echo \" adapter: $ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER\" >> /data/configuration.yaml;\n echo \"##########################################################\" >> /data/configuration.yaml;\n echo 'Initial configuration file created at \"/data/configuration.yaml\"';\nfi;\n"` | | +| initContainers.init-config.command[0] | string | `"/bin/sh"` | | +| initContainers.init-config.command[1] | string | `"-c"` | | +| initContainers.init-config.env[0].name | string | `"ZIGBEE2MQTT_CONFIG_FRONTEND_PORT"` | | +| initContainers.init-config.env[0].value | string | `"{{ .Values.service.main.ports.main.port }}"` | | +| initContainers.init-config.env[1].name | string | `"ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API"` | | +| initContainers.init-config.env[1].value | string | `"{{ .Values.env.ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API }}"` | | +| initContainers.init-config.env[2].name | string | `"ZIGBEE2MQTT_CONFIG_PERMIT_JOIN"` | | +| initContainers.init-config.env[2].value | string | `"{{ .Values.env.ZIGBEE2MQTT_CONFIG_PERMIT_JOIN }}"` | | +| initContainers.init-config.env[3].name | string | `"ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API"` | | +| initContainers.init-config.env[3].value | string | `"{{ .Values.env.ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API }}"` | | +| initContainers.init-config.env[4].name | string | `"ZIGBEE2MQTT_CONFIG_MQTT_SERVER"` | | +| initContainers.init-config.env[4].value | string | `"{{ .Values.env.ZIGBEE2MQTT_CONFIG_MQTT_SERVER }}"` | | +| initContainers.init-config.env[5].name | string | `"ZIGBEE2MQTT_CONFIG_MQTT_USER"` | | +| initContainers.init-config.env[5].value | string | `"{{ .Values.secret.ZIGBEE2MQTT_CONFIG_MQTT_USER }}"` | | +| initContainers.init-config.env[6].name | string | `"ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD"` | | +| initContainers.init-config.env[6].value | string | `"{{ .Values.secret.ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD }}"` | | +| initContainers.init-config.env[7].name | string | `"ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC"` | | +| initContainers.init-config.env[7].value | string | `"{{ .Values.env.ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC }}"` | | +| initContainers.init-config.env[8].name | string | `"ZIGBEE2MQTT_CONFIG_SERIAL_PORT"` | | +| initContainers.init-config.env[8].value | string | `"{{ .Values.env.ZIGBEE2MQTT_CONFIG_SERIAL_PORT }}"` | | +| initContainers.init-config.env[9].name | string | `"ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER"` | | +| initContainers.init-config.env[9].value | string | `"{{ .Values.env.ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER }}"` | | +| initContainers.init-config.image | string | `"{{ .Values.image.repository }}:{{ .Values.image.tag }}"` | | +| initContainers.init-config.volumeMounts[0].mountPath | string | `"/data"` | | +| initContainers.init-config.volumeMounts[0].name | string | `"data"` | | +| persistence.data.enabled | bool | `true` | | +| persistence.data.mountPath | string | `"/data"` | | +| podSecurityContext.runAsGroup | int | `0` | | +| podSecurityContext.runAsUser | int | `0` | | +| secret.ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD | string | `""` | | +| secret.ZIGBEE2MQTT_CONFIG_MQTT_USER | string | `""` | | +| securityContext.readOnlyRootFilesystem | bool | `false` | | +| securityContext.runAsNonRoot | bool | `false` | | +| service.main.ports.main.port | int | `10103` | | + +All Rights Reserved - The TrueCharts Project diff --git a/stable/zigbee2mqtt/2.0.8/ix_values.yaml b/stable/zigbee2mqtt/2.0.8/ix_values.yaml new file mode 100644 index 00000000000..093350786ce --- /dev/null +++ b/stable/zigbee2mqtt/2.0.8/ix_values.yaml @@ -0,0 +1,101 @@ +image: + repository: tccr.io/truecharts/zigbee2mqtt + tag: v1.24.0@sha256:2574cbd6af36d0305c8034804e2c64f672757133d71b14f87f36913a9b97e754 + pullPolicy: IfNotPresent + +secret: + ZIGBEE2MQTT_CONFIG_MQTT_USER: "" + ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD: "" + +env: + ZIGBEE2MQTT_DATA: "/data" + ZIGBEE2MQTT_CONFIG_FRONTEND_PORT: "{{ .Values.service.main.ports.main.port }}" + ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API: true + # User defined + ZIGBEE2MQTT_CONFIG_PERMIT_JOIN: true + ZIGBEE2MQTT_CONFIG_MQTT_SERVER: "mqtt://localhost" + ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC: "zigbee2mqtt" + ZIGBEE2MQTT_CONFIG_SERIAL_PORT: "/dev/ttyUSB0" + ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER: "auto" + +securityContext: + runAsNonRoot: false + readOnlyRootFilesystem: false + +podSecurityContext: + runAsUser: 0 + runAsGroup: 0 + +service: + main: + ports: + main: + port: 10103 + +persistence: + data: + enabled: true + mountPath: "/data" + +initContainers: + init-config: + image: "{{ .Values.image.repository }}:{{ .Values.image.tag }}" + volumeMounts: + - name: data + mountPath: "/data" + env: + - name: ZIGBEE2MQTT_CONFIG_FRONTEND_PORT + value: "{{ .Values.service.main.ports.main.port }}" + - name: ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API + value: "{{ .Values.env.ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API }}" + - name: ZIGBEE2MQTT_CONFIG_PERMIT_JOIN + value: "{{ .Values.env.ZIGBEE2MQTT_CONFIG_PERMIT_JOIN }}" + - name: ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API + value: "{{ .Values.env.ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API }}" + - name: ZIGBEE2MQTT_CONFIG_MQTT_SERVER + value: "{{ .Values.env.ZIGBEE2MQTT_CONFIG_MQTT_SERVER }}" + - name: ZIGBEE2MQTT_CONFIG_MQTT_USER + value: "{{ .Values.secret.ZIGBEE2MQTT_CONFIG_MQTT_USER }}" + - name: ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD + value: "{{ .Values.secret.ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD }}" + - name: ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC + value: "{{ .Values.env.ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC }}" + - name: ZIGBEE2MQTT_CONFIG_SERIAL_PORT + value: "{{ .Values.env.ZIGBEE2MQTT_CONFIG_SERIAL_PORT }}" + - name: ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER + value: "{{ .Values.env.ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER }}" + command: ["/bin/sh", "-c"] + args: + - > + if [ -f /data/configuration.yaml ]; + then + echo "Initial configuration exists. Skipping"; + else + echo "Creating initial configuration"; + touch /data/configuration.yaml; + echo "# Configuration bellow will be always be overridden" >> /data/configuration.yaml; + echo "# from environment settings on the Scale Apps UI." >> /data/configuration.yaml; + echo "# You however will not see this values change in the file." >> /data/configuration.yaml; + echo "##########################################################" >> /data/configuration.yaml; + echo "experimental:" >> /data/configuration.yaml; + echo " new_api: $ZIGBEE2MQTT_CONFIG_EXPIRIMENTAL_NEW_API" >> /data/configuration.yaml; + echo "frontend:" >> /data/configuration.yaml; + echo " port: $ZIGBEE2MQTT_CONFIG_FRONTEND_PORT" >> /data/configuration.yaml; + echo "permit_join: $ZIGBEE2MQTT_CONFIG_PERMIT_JOIN" >> /data/configuration.yaml; + echo "mqtt:" >> /data/configuration.yaml; + echo " server: $ZIGBEE2MQTT_CONFIG_MQTT_SERVER" >> /data/configuration.yaml; + echo " base_topic: $ZIGBEE2MQTT_CONFIG_MQTT_BASE_TOPIC" >> /data/configuration.yaml; + if [ ! -z "$ZIGBEE2MQTT_CONFIG_MQTT_USER" ]; + then + echo " user: $ZIGBEE2MQTT_CONFIG_MQTT_USER" >> /data/configuration.yaml; + fi; + if [ ! -z "$ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD" ]; + then + echo " password: $ZIGBEE2MQTT_CONFIG_MQTT_PASSWORD" >> /data/configuration.yaml; + fi; + echo "serial:" >> /data/configuration.yaml; + echo " port: $ZIGBEE2MQTT_CONFIG_SERIAL_PORT" >> /data/configuration.yaml; + echo " adapter: $ZIGBEE2MQTT_CONFIG_SERIAL_ADAPTER" >> /data/configuration.yaml; + echo "##########################################################" >> /data/configuration.yaml; + echo 'Initial configuration file created at "/data/configuration.yaml"'; + fi; diff --git a/stable/zigbee2mqtt/2.0.7/questions.yaml b/stable/zigbee2mqtt/2.0.8/questions.yaml similarity index 99% rename from stable/zigbee2mqtt/2.0.7/questions.yaml rename to stable/zigbee2mqtt/2.0.8/questions.yaml index 05265456a96..155960d1c82 100644 --- a/stable/zigbee2mqtt/2.0.7/questions.yaml +++ b/stable/zigbee2mqtt/2.0.8/questions.yaml @@ -477,7 +477,7 @@ questions: description: "The internal(!) port on the container the Application runs on" schema: type: int - default: 8080 + default: 10103 - variable: serviceexpert group: "Networking and Services" @@ -1512,7 +1512,7 @@ questions: label: "ReadOnly Root Filesystem" schema: type: boolean - default: true + default: false - variable: allowPrivilegeEscalation label: "Allow Privilege Escalation" schema: diff --git a/stable/zigbee2mqtt/2.0.7/security.md b/stable/zigbee2mqtt/2.0.8/security.md similarity index 91% rename from stable/zigbee2mqtt/2.0.7/security.md rename to stable/zigbee2mqtt/2.0.8/security.md index b1349fbe186..18d4b66cd43 100644 --- a/stable/zigbee2mqtt/2.0.7/security.md +++ b/stable/zigbee2mqtt/2.0.8/security.md @@ -18,24 +18,35 @@ hide: | Type | Misconfiguration ID | Check | Severity | Explaination | Links | |:----------------|:------------------:|:-----------:|:------------------:|-----------------------------------------|-----------------------------------------| | Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM |
Expand... A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.allowPrivilegeEscalation' to false
|
Expand...https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted
https://avd.aquasec.com/appshield/ksv001
| +| Kubernetes Security Check | KSV001 | Process can elevate its own privileges | MEDIUM |
Expand... A program inside the container can elevate its own privileges and run as root, which might give the program control over the container and node.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.allowPrivilegeEscalation' to false
|
Expand...https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted
https://avd.aquasec.com/appshield/ksv001
| | Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW |
Expand... The container should drop all default capabilities and add only those that are needed for its execution.

Container 'RELEASE-NAME-zigbee2mqtt' of Deployment 'RELEASE-NAME-zigbee2mqtt' should add 'ALL' to 'securityContext.capabilities.drop'
|
Expand...https://kubesec.io/basics/containers-securitycontext-capabilities-drop-index-all/
https://avd.aquasec.com/appshield/ksv003
| | Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW |
Expand... The container should drop all default capabilities and add only those that are needed for its execution.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should add 'ALL' to 'securityContext.capabilities.drop'
|
Expand...https://kubesec.io/basics/containers-securitycontext-capabilities-drop-index-all/
https://avd.aquasec.com/appshield/ksv003
| +| Kubernetes Security Check | KSV003 | Default capabilities not dropped | LOW |
Expand... The container should drop all default capabilities and add only those that are needed for its execution.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should add 'ALL' to 'securityContext.capabilities.drop'
|
Expand...https://kubesec.io/basics/containers-securitycontext-capabilities-drop-index-all/
https://avd.aquasec.com/appshield/ksv003
| | Kubernetes Security Check | KSV011 | CPU not limited | LOW |
Expand... Enforcing CPU limits prevents DoS via resource exhaustion.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'resources.limits.cpu'
|
Expand...https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-resource-requests-and-limits
https://avd.aquasec.com/appshield/ksv011
| +| Kubernetes Security Check | KSV011 | CPU not limited | LOW |
Expand... Enforcing CPU limits prevents DoS via resource exhaustion.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'resources.limits.cpu'
|
Expand...https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-resource-requests-and-limits
https://avd.aquasec.com/appshield/ksv011
| | Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM |
Expand... 'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.

Container 'RELEASE-NAME-zigbee2mqtt' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsNonRoot' to true
|
Expand...https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted
https://avd.aquasec.com/appshield/ksv012
| | Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM |
Expand... 'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.

Container 'autopermissions' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsNonRoot' to true
|
Expand...https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted
https://avd.aquasec.com/appshield/ksv012
| | Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM |
Expand... 'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsNonRoot' to true
|
Expand...https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted
https://avd.aquasec.com/appshield/ksv012
| +| Kubernetes Security Check | KSV012 | Runs as root user | MEDIUM |
Expand... 'runAsNonRoot' forces the running image to run as a non-root user to ensure least privileges.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsNonRoot' to true
|
Expand...https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted
https://avd.aquasec.com/appshield/ksv012
| +| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW |
Expand... An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.

Container 'RELEASE-NAME-zigbee2mqtt' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.readOnlyRootFilesystem' to true
|
Expand...https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/
https://avd.aquasec.com/appshield/ksv014
| | Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW |
Expand... An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.

Container 'autopermissions' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.readOnlyRootFilesystem' to true
|
Expand...https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/
https://avd.aquasec.com/appshield/ksv014
| | Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW |
Expand... An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.readOnlyRootFilesystem' to true
|
Expand...https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/
https://avd.aquasec.com/appshield/ksv014
| +| Kubernetes Security Check | KSV014 | Root file system is not read-only | LOW |
Expand... An immutable root file system prevents applications from writing to their local disk. This can limit intrusions, as attackers will not be able to tamper with the file system or write foreign executables to disk.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.readOnlyRootFilesystem' to true
|
Expand...https://kubesec.io/basics/containers-securitycontext-readonlyrootfilesystem-true/
https://avd.aquasec.com/appshield/ksv014
| | Kubernetes Security Check | KSV015 | CPU requests not specified | LOW |
Expand... When containers have resource requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'resources.requests.cpu'
|
Expand...https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-resource-requests-and-limits
https://avd.aquasec.com/appshield/ksv015
| +| Kubernetes Security Check | KSV015 | CPU requests not specified | LOW |
Expand... When containers have resource requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'resources.requests.cpu'
|
Expand...https://cloud.google.com/blog/products/containers-kubernetes/kubernetes-best-practices-resource-requests-and-limits
https://avd.aquasec.com/appshield/ksv015
| | Kubernetes Security Check | KSV016 | Memory requests not specified | LOW |
Expand... When containers have memory requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'resources.requests.memory'
|
Expand...https://kubesec.io/basics/containers-resources-limits-memory/
https://avd.aquasec.com/appshield/ksv016
| +| Kubernetes Security Check | KSV016 | Memory requests not specified | LOW |
Expand... When containers have memory requests specified, the scheduler can make better decisions about which nodes to place pods on, and how to deal with resource contention.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'resources.requests.memory'
|
Expand...https://kubesec.io/basics/containers-resources-limits-memory/
https://avd.aquasec.com/appshield/ksv016
| | Kubernetes Security Check | KSV017 | Privileged container | HIGH |
Expand... Privileged containers share namespaces with the host system and do not offer any security. They should be used exclusively for system containers that require high privileges.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.privileged' to false
|
Expand...https://kubernetes.io/docs/concepts/security/pod-security-standards/#baseline
https://avd.aquasec.com/appshield/ksv017
| | Kubernetes Security Check | KSV018 | Memory not limited | LOW |
Expand... Enforcing memory limits prevents DoS via resource exhaustion.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'resources.limits.memory'
|
Expand...https://kubesec.io/basics/containers-resources-limits-memory/
https://avd.aquasec.com/appshield/ksv018
| +| Kubernetes Security Check | KSV018 | Memory not limited | LOW |
Expand... Enforcing memory limits prevents DoS via resource exhaustion.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'resources.limits.memory'
|
Expand...https://kubesec.io/basics/containers-resources-limits-memory/
https://avd.aquasec.com/appshield/ksv018
| | Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM |
Expand... Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.

Container 'RELEASE-NAME-zigbee2mqtt' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsUser' > 10000
|
Expand...https://kubesec.io/basics/containers-securitycontext-runasuser/
https://avd.aquasec.com/appshield/ksv020
| | Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM |
Expand... Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.

Container 'autopermissions' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsUser' > 10000
|
Expand...https://kubesec.io/basics/containers-securitycontext-runasuser/
https://avd.aquasec.com/appshield/ksv020
| | Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM |
Expand... Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsUser' > 10000
|
Expand...https://kubesec.io/basics/containers-securitycontext-runasuser/
https://avd.aquasec.com/appshield/ksv020
| +| Kubernetes Security Check | KSV020 | Runs with low user ID | MEDIUM |
Expand... Force the container to run with user ID > 10000 to avoid conflicts with the host’s user table.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsUser' > 10000
|
Expand...https://kubesec.io/basics/containers-securitycontext-runasuser/
https://avd.aquasec.com/appshield/ksv020
| | Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM |
Expand... Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.

Container 'RELEASE-NAME-zigbee2mqtt' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsGroup' > 10000
|
Expand...https://kubesec.io/basics/containers-securitycontext-runasuser/
https://avd.aquasec.com/appshield/ksv021
| | Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM |
Expand... Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.

Container 'autopermissions' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsGroup' > 10000
|
Expand...https://kubesec.io/basics/containers-securitycontext-runasuser/
https://avd.aquasec.com/appshield/ksv021
| | Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM |
Expand... Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.

Container 'hostpatch' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsGroup' > 10000
|
Expand...https://kubesec.io/basics/containers-securitycontext-runasuser/
https://avd.aquasec.com/appshield/ksv021
| +| Kubernetes Security Check | KSV021 | Runs with low group ID | MEDIUM |
Expand... Force the container to run with group ID > 10000 to avoid conflicts with the host’s user table.

Container 'init-config' of Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'securityContext.runAsGroup' > 10000
|
Expand...https://kubesec.io/basics/containers-securitycontext-runasuser/
https://avd.aquasec.com/appshield/ksv021
| | Kubernetes Security Check | KSV023 | hostPath volumes mounted | MEDIUM |
Expand... HostPath volumes must be forbidden.

Deployment 'RELEASE-NAME-zigbee2mqtt' should not set 'spec.template.volumes.hostPath'
|
Expand...https://kubernetes.io/docs/concepts/security/pod-security-standards/#baseline
https://avd.aquasec.com/appshield/ksv023
| | Kubernetes Security Check | KSV029 | A root primary or supplementary GID set | LOW |
Expand... Containers should be forbidden from running with a root primary or supplementary GID.

Deployment 'RELEASE-NAME-zigbee2mqtt' should set 'spec.securityContext.runAsGroup', 'spec.securityContext.supplementalGroups[*]' and 'spec.securityContext.fsGroup' to integer greater than 0
|
Expand...https://kubernetes.io/docs/concepts/security/pod-security-standards/#restricted
https://avd.aquasec.com/appshield/ksv029
| @@ -45,6 +56,7 @@ hide: tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c tccr.io/truecharts/alpine:v3.14.2@sha256:4095394abbae907e94b1f2fd2e2de6c4f201a5b9704573243ca8eb16db8cdb7c + 'tccr.io/truecharts/zigbee2mqtt:v1.24.0@sha256:2574cbd6af36d0305c8034804e2c64f672757133d71b14f87f36913a9b97e754' tccr.io/truecharts/zigbee2mqtt:v1.24.0@sha256:2574cbd6af36d0305c8034804e2c64f672757133d71b14f87f36913a9b97e754 ##### Scan Results @@ -118,6 +130,8 @@ hide: | ssl_client | CVE-2021-42375 | MEDIUM | 1.33.1-r3 | 1.33.1-r5 |
Expand...https://jfrog.com/blog/unboxing-busybox-14-new-vulnerabilities-uncovered-by-claroty-and-jfrog/
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6T2TURBYYJGBMQTTN2DSOAIQGP7WCPGV/
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UQXGOGWBIYWOIVXJVRKHZR34UMEHQBXS/
https://security.netapp.com/advisory/ntap-20211223-0002/
| + + #### Container: tccr.io/truecharts/zigbee2mqtt:v1.24.0@sha256:2574cbd6af36d0305c8034804e2c64f672757133d71b14f87f36913a9b97e754 (alpine 3.12.9) diff --git a/stable/zigbee2mqtt/2.0.7/templates/common.yaml b/stable/zigbee2mqtt/2.0.8/templates/common.yaml similarity index 100% rename from stable/zigbee2mqtt/2.0.7/templates/common.yaml rename to stable/zigbee2mqtt/2.0.8/templates/common.yaml diff --git a/stable/zigbee2mqtt/2.0.7/values.yaml b/stable/zigbee2mqtt/2.0.8/values.yaml similarity index 100% rename from stable/zigbee2mqtt/2.0.7/values.yaml rename to stable/zigbee2mqtt/2.0.8/values.yaml