From 2aa98755b4c203677fe35e3e5a3564dfe285e18f Mon Sep 17 00:00:00 2001 From: Alex Manning Date: Thu, 2 Mar 2023 21:32:04 +0000 Subject: [PATCH] Mqtt chart.yaml --- charts/mqtt/Chart.yaml | 22 ++-------------------- 1 file changed, 2 insertions(+), 20 deletions(-) diff --git a/charts/mqtt/Chart.yaml b/charts/mqtt/Chart.yaml index ade65d0..f78e532 100644 --- a/charts/mqtt/Chart.yaml +++ b/charts/mqtt/Chart.yaml @@ -1,24 +1,6 @@ apiVersion: v2 name: mqtt -description: A Helm chart for Kubernetes - -# A chart can be either an 'application' or a 'library' chart. -# -# Application charts are a collection of templates that can be packaged into versioned archives -# to be deployed. -# -# Library charts provide useful utilities or functions for the chart developer. They're included as -# a dependency of application charts to inject those utilities and functions into the rendering -# pipeline. Library charts do not define any templates and therefore cannot be deployed. +description: A Helm chart for MQTT type: application - -# 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: 0.1.0 - -# 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: "1.16.0" +appVersion: "2.0.14"