Modified chart name and corrected semantic versioning

charts/tfy-gpu-operator/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: tfy-gpu-operator
-version: 0.0.2
+version: 0.1.0
 description: "Truefoundry GPU Operator"
 maintainers:
   - name: truefoundry

charts/tfy-istio-ingress/Chart.yaml

@@ -1,6 +1,6 @@
 apiVersion: v2
 name: tfy-istio-ingress
-version: 0.0.6
+version: 0.1.0
 description: "ArgoCD Applications for istio ingress config"
 maintainers:
   - name: truefoundry

charts/tfy-karpenter-config/.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/tfy-karpenter-config/Chart.yaml

@@ -0,0 +1,18 @@
+apiVersion: v2
+name: tfy-karpenter-config
+description: "ArgoCD Applications for karpenter config"
+
+# 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