rancher-partner-charts/packages/dkube/generated-changes/patch/Chart.yaml.patch

41 lines
1.8 KiB
Diff

--- charts-original/Chart.yaml
+++ charts/Chart.yaml
@@ -1,22 +1,22 @@
apiVersion: v2
name: dkube-deployer
-description: A Helm chart for Dkube product installation on kubernetes platform
-
-# 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 Kubernetes-based MLOps platform based on open standards Kubeflow and MLflow
+home: https://dkube.io
+icon: https://www.dkube.io/img/logo_new.png
+keywords:
+- kubernetes
+- MLOps
+- Kubeflow
+- AI
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: 1.0.6
-# 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.
-appVersion:
+# Application version
+appVersion: "3.2.0.1"
+annotations:
+ catalog.cattle.io/certified: partner # Enables the "partner" badge in the UI for easier identification
+ catalog.cattle.io/release-name: dkube # Your chart's name in kebab-case, this is used for deployment
+ catalog.cattle.io/display-name: Dkube # The chart's name you want displayed in the UI
+kubeVersion: "1.20"