diff --git a/helm/Chart.yaml b/helm/Chart.yaml index de0da97..bc2b246 100644 --- a/helm/Chart.yaml +++ b/helm/Chart.yaml @@ -1,24 +1,6 @@ apiVersion: v2 name: squid-exporter -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 to deploy Squid Exporter. 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: "v1.10.3" diff --git a/helm/values.yaml b/helm/values.yaml index fce0c97..788c555 100644 --- a/helm/values.yaml +++ b/helm/values.yaml @@ -70,12 +70,6 @@ service: # for more information. nodePort: "" -# Please pay attention that Kubernetes Ingress -# is designed to handle HTTP or HTTPS traffic and not proxy protocol -# so if you need to use Ingress, please ensure that your Ingress Controller -# can properly forward PROXY requests (possibly via Ingress Controller specific annotations). -# If it is not possible, Squid should be used either via in-cluster ClusterIP -# Service or via NodePort and/or LoadBalancer Kubernetes Service type. ingress: enabled: false className: ""