add chart for dashboards

Signed-off-by: Sanket <[email protected]>

charts/ai-stack/Chart.yaml

@@ -16,7 +16,7 @@ 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.3.6
+version: 0.3.7
 
 # 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

charts/ai-stack/values.yaml

@@ -185,12 +185,3 @@ reranker:
     - name: hf-cache
       persistentVolumeClaim:
         claimName: hf-cache
-
-## Enable Grafana Dashboard configmaps for auto dashboard provisioning
-## If you use kube-prometheus stack for monitoring, these will get imported into grafana
-grafana:
-  ## The namespace in which grafana pod is present
-  namespace: monitoring
-  dashboards:
-    ## Disabled by default. switch to true to deploy them
-    enable: false

charts/infracloud-dashboards/.helmignore

@@ -0,0 +1,23 @@
+# Patterns to ignore when building packages.
+# This supports shell glob matching, relative path matching, and
+# negation (prefixed with !). Only one pattern per line.
+.DS_Store
+# Common VCS dirs
+.git/
+.gitignore
+.bzr/
+.bzrignore
+.hg/
+.hgignore
+.svn/
+# Common backup files
+*.swp
+*.bak
+*.tmp
+*.orig
+*~
+# Various IDEs
+.project
+.idea/
+*.tmproj
+.vscode/

charts/infracloud-dashboards/Chart.yaml

@@ -0,0 +1,24 @@
+apiVersion: v2
+name: infracloud-dashboards
+description: A Helm chart for deploying Grafana dashboards for InfraCloud
+
+# 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.
+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"