Make the linters happy

Signed-off-by: Pete Wall <pete.wall@grafana.com>

charts/feature-annotation-autodiscovery/README.md

@@ -8,7 +8,7 @@
 ![Version: 1.0.0](https://img.shields.io/badge/Version-1.0.0-informational?style=flat-square) ![AppVersion: 1.0.0](https://img.shields.io/badge/AppVersion-1.0.0-informational?style=flat-square)
 Gathers metrics automatically based on Kubernetes Pod and Service annotations
 
-The annotation-based autodiscovery feature makes it very simple to add scrape targets. With this feature enabled, any
+The annotation-based autodiscovery feature makes it easy to add scrape targets. With this feature enabled, any
 Kubernetes Pods or Services with the `k8s.grafana.com/scrape` annotation set to `true` will be automatically discovered
 and scraped by the collector. There are several other annotations that can be used to customize the behavior of the
 scrape configuration, such as:

charts/feature-annotation-autodiscovery/README.md.gotmpl

@@ -9,7 +9,7 @@
 {{ template "chart.description" . }}
 {{ template "chart.homepageLine" . }}
 
-The annotation-based autodiscovery feature makes it very simple to add scrape targets. With this feature enabled, any
+The annotation-based autodiscovery feature makes it easy to add scrape targets. With this feature enabled, any
 Kubernetes Pods or Services with the `k8s.grafana.com/scrape` annotation set to `true` will be automatically discovered
 and scraped by the collector. There are several other annotations that can be used to customize the behavior of the
 scrape configuration, such as:

charts/k8s-monitoring/docs/examples/auth/bearer-token/README.md

@@ -11,6 +11,7 @@ token inside the values file. The Loki destination gets a bearer token from an e
 ## Values
 
 ```yaml
+---
 cluster:
   name: bearer-token-example-cluster
 

charts/k8s-monitoring/docs/examples/auth/bearer-token/values.yaml

@@ -1,3 +1,4 @@
+---
 cluster:
   name: bearer-token-example-cluster
 

charts/k8s-monitoring/docs/examples/auth/embedded-secrets/README.md

@@ -10,6 +10,7 @@ secret data directly into the destination configuration.
 ## Values
 
 ```yaml
+---
 cluster:
   name: embedded-secrets-example-cluster
 

charts/k8s-monitoring/docs/examples/auth/embedded-secrets/values.yaml

@@ -1,3 +1,4 @@
+---
 cluster:
   name: embedded-secrets-example-cluster
 

charts/k8s-monitoring/docs/examples/auth/external-secrets/README.md

@@ -7,10 +7,10 @@
 This example demonstrates how to use pre-existing secrets to authenticate to external services. This allows for
 credentials to be stored in different secret stores, as long as it resolves to a Kubernetes Secret.
 
-
 ## Values
 
 ```yaml
+---
 cluster:
   name: external-secrets-example-cluster
 

charts/k8s-monitoring/docs/examples/auth/external-secrets/description.txt

@@ -2,4 +2,3 @@
 
 This example demonstrates how to use pre-existing secrets to authenticate to external services. This allows for
 credentials to be stored in different secret stores, as long as it resolves to a Kubernetes Secret.
-

charts/k8s-monitoring/docs/examples/auth/external-secrets/values.yaml

@@ -1,3 +1,4 @@
+---
 cluster:
   name: external-secrets-example-cluster
 

charts/k8s-monitoring/docs/examples/autoscaling/README.md

@@ -10,6 +10,7 @@ down based on its CPU and memory utilization.
 ## Values
 
 ```yaml
+---
 cluster:
   name: autoscaling-example-cluster
 

charts/k8s-monitoring/docs/examples/autoscaling/values.yaml

@@ -1,3 +1,4 @@
+---
 cluster:
   name: autoscaling-example-cluster
 

charts/k8s-monitoring/docs/examples/collector-storage/README.md

@@ -11,6 +11,7 @@ store log file positions, so it knows where to start reading logs from after a r
 ## Values
 
 ```yaml
+---
 cluster:
   name: collector-storage-example-cluster
 
@@ -64,4 +65,5 @@ alloy-logs:
         - name: alloy-log-positions
           hostPath:
             path: /var/alloy-log-storage
-            type: DirectoryOrCreate```
+            type: DirectoryOrCreate
+```

charts/k8s-monitoring/docs/examples/collector-storage/values.yaml

@@ -1,3 +1,4 @@
+---
 cluster:
   name: collector-storage-example-cluster
 
@@ -51,4 +52,4 @@ alloy-logs:
         - name: alloy-log-positions
           hostPath:
             path: /var/alloy-log-storage
-            type: DirectoryOrCreate
+            type: DirectoryOrCreate

charts/k8s-monitoring/docs/examples/platforms/azure-aks/README.md

@@ -59,4 +59,5 @@ alloy-singleton:
 alloy-logs:
   enabled: true
   controller:
-    podAnnotations: {kubernetes.azure.com/set-kube-service-host-fqdn: "true"}```
+    podAnnotations: {kubernetes.azure.com/set-kube-service-host-fqdn: "true"}
+```

charts/k8s-monitoring/docs/examples/platforms/azure-aks/values.yaml

@@ -33,4 +33,4 @@ alloy-singleton:
 alloy-logs:
   enabled: true
   controller:
-    podAnnotations: {kubernetes.azure.com/set-kube-service-host-fqdn: "true"}
+    podAnnotations: {kubernetes.azure.com/set-kube-service-host-fqdn: "true"}

charts/k8s-monitoring/docs/examples/private-image-registries/README.md

@@ -15,6 +15,7 @@ If you do not want to use the `global` object, registry and pull secrets can be
 ## Values
 
 ```yaml
+---
 cluster:
   name: private-image-registries-example-cluster
 

charts/k8s-monitoring/docs/examples/private-image-registries/values.yaml

@@ -1,3 +1,4 @@
+---
 cluster:
   name: private-image-registries-example-cluster
 

examples/README.md

@@ -2,5 +2,5 @@
 
 Examples have been moved into their own chart directories.
 
-* K8s Monitoring Helm chart v1.x: [v1 chart examples](../charts/k8s-monitoring-v1/docs/examples)
-* K8s Monitoring Helm chart v2.x: [v2 chart examples](../charts/k8s-monitoring/docs/examples)
+*   K8s Monitoring Helm chart v1.x: [v1 chart examples](../charts/k8s-monitoring-v1/docs/examples)
+*   K8s Monitoring Helm chart v2.x: [v2 chart examples](../charts/k8s-monitoring/docs/examples)

scripts/lint-markdown.sh

@@ -15,7 +15,8 @@ fi
 (return 0 2>/dev/null) && sourced=1 || sourced=0
 
 statusCode=0
-./node_modules/.bin/markdownlint-cli2 ./*.md ./**/*.md "#node_modules" "#data-alloy" "#charts/**/data-alloy"
+# shellcheck disable=SC2046
+./node_modules/.bin/markdownlint-cli2 $(find . -name "*.md" ! -path "./node_modules/*" ! -path "./data-alloy/*" ! -path "./charts/**/data-alloy/*")
 currentCode="$?"
 # only override the statusCode if it is 0
 if [[ "${statusCode}" == 0 ]]; then

scripts/lint-shell.sh

@@ -19,10 +19,10 @@ statusCode=0
 # shellcheck disable=SC2046 disable=SC2312
 shellcheck --rcfile="$(pwd)/.shellcheckrc" $(
     comm -23 <(
-      find . -type f -name "*.sh" -not \( -path "./node_modules/*" -o -path "./data-alloy/*" -o -path "./.git/*" -o -path "./charts/k8s-monitoring-v1/test/spec/*" \) | \
+      find . -type f -name "*.sh" -not \( -path "./node_modules/*" -o -path "./data-alloy/*" -o -path "./.git/*" -o -path "./charts/k8s-monitoring-v1/test/spec/*" -o -path "./charts/k8s-monitoring/tests/example-checks/spec/*" \) | \
         sort
       ) <(
-      find . -type f -name "*.sh"  -not \( -path "./node_modules/*" -o -path "./data-alloy/*" -o -path "./.git/*" -o -path "./charts/k8s-monitoring-v1/test/spec/*" \) | \
+      find . -type f -name "*.sh"  -not \( -path "./node_modules/*" -o -path "./data-alloy/*" -o -path "./.git/*" -o -path "./charts/k8s-monitoring-v1/test/spec/*" -o -path "./charts/k8s-monitoring/tests/example-checks/spec/*" \) | \
         git check-ignore --stdin | \
         sort
       )