From 3012f764d37c456d1fbb65d973bddbb6e09c1d09 Mon Sep 17 00:00:00 2001 From: William P Date: Mon, 24 Feb 2025 11:41:15 -0500 Subject: [PATCH] oops --- system-apps/velero/Chart.yaml | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/system-apps/velero/Chart.yaml b/system-apps/velero/Chart.yaml index e69de29..7359475 100644 --- a/system-apps/velero/Chart.yaml +++ b/system-apps/velero/Chart.yaml @@ -0,0 +1,28 @@ +apiVersion: v2 +name: velero +description: A Helm chart for Kubernetes + +# 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. +appVersion: "1.0" + +dependencies: +- name: velero + version: 8.4.0 + repository: https://vmware-tanzu.github.io/helm-charts \ No newline at end of file