[Adguard-home] Allow to mount secret with certs so we can set the tls … (#87)

* Adguard-home: Allow to mount secret with certs so we can set the tls configs with these

* adguard-home bump to 2.2.0

charts/adguard-home/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 appVersion: v0.102.0
 description: DNS proxy as ad-blocker for local network
 name: adguard-home
-version: 2.1.1
+version: 2.2.0
 keywords:
   - adguard-home
   - adguard

charts/adguard-home/templates/deployment.yaml

@@ -83,6 +83,11 @@ spec:
             - name: config
               mountPath: /opt/adguardhome/conf
               readOnly: false
+            {{- if .Values.tlsSecretName }}
+            - name: certs
+              mountPath: /certs
+              readOnly: false
+            {{- end }}
           ports:
             - name: http
               {{- if .Values.configAsCode.enabled }}
@@ -153,6 +158,11 @@ spec:
           resources:
             {{- toYaml .Values.resources | nindent 12 }}
       volumes:
+      {{- if .Values.tlsSecretName }}
+      - name: certs
+        secret:
+          secretName: {{ .Values.tlsSecretName }}
+      {{- end }}
       {{- if .Values.configAsCode.enabled }}
       - name: configmap
         configMap:

charts/adguard-home/values.yaml

@@ -165,6 +165,10 @@ configAsCode:
     verbose: false
     schema_version: 6
 
+tlsSecretName: ""
+# name of the secret that contains the tls cert and key.
+# this secret will be mounted inside the adguard container /certs path. e.g. works with cert-manager
+
 image:
   repository: adguard/adguardhome
   # Image tag is set via charts appVersion. If you want to override the tag, specify it here

charts/media-common/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 name: media-common
 description: Common dependancy chart for media ecosystem containers
 type: application
-version: 1.3.0
+version: 1.3.1
 keywords:
   - media-common
 home: https://github.com/k8s-at-home/charts/tree/master/charts/media-common

charts/media-common/templates/ingress.yaml

@@ -64,7 +64,7 @@ kind: Ingress
 metadata:
   name: {{ $fullName }}-{{ $ingress.nameSuffix | default $index }}
   labels:
-    {{- include "media-common.labels" . | nindent 4 }}
+    {{- include "media-common.labels" $ | nindent 4 }}
     {{- with $ingress.annotations }}
   annotations:
   {{- toYaml . | nindent 4 }}

charts/uptimerobot-prometheus/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 name: uptimerobot-prometheus
 description: Prometheus Exporter for the official uptimerobot CLI
 type: application
-version: 2.0.0
+version: 2.0.1
 appVersion: 0.0.1
 keywords:
 - uptimerobot

charts/uptimerobot-prometheus/templates/service.yaml

@@ -4,6 +4,10 @@ metadata:
   name: {{ include "uptimerobot-prometheus.fullname" . }}
   labels:
     {{- include "uptimerobot-prometheus.labels" . | nindent 4 }}
+{{- if .Values.service.annotations }}
+  annotations:
+{{ toYaml .Values.service.annotations | indent 4 }}
+{{- end }}
 spec:
   type: {{ .Values.service.type }}
   ports:

charts/uptimerobot-prometheus/values.yaml

@@ -29,6 +29,10 @@ securityContext: {}
 service:
   type: ClusterIP
   port: 9705
+  # Sometimes you may need to add annotations to the service
+  # to integrate with external operators
+  # annotations:
+    # prometheus.io/scrape: "true"
 
 resources: {}
   # We usually recommend not to specify default resources and to leave this as a conscious

charts/zigbee2mqtt/Chart.yaml

@@ -3,7 +3,7 @@ name: zigbee2mqtt
 type: application
 description: Bridges events and allows you to control your Zigbee devices via MQTT
 appVersion: 1.15.0
-version: 2.0.0
+version: 2.0.1
 keywords:
   - zigbee
   - mqtt