Closed clickersmudge closed 5 months ago
I made a mistake. It works
Valid Chart.yaml
apiVersion: v2
name: volume-autoscaler
description: Volume Autoscaler scales Kubernetes volumes up automatically based on metrics from Prometheus, helm chart based on Universal Helm Charts from DevOps Nirvana
# 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: 1.0.8
# 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.8"
dependencies:
- name: volume-autoscaler
version: 1.0.8
repository: https://devops-nirvana.s3.amazonaws.com/helm-charts/
Version 1.0.8
from https://devops-nirvana.s3.amazonaws.com/helm-charts/index.yaml
Describe the bug Problem with the repository when installing with ArgoCD
To Reproduce I set up the whole deployment in Argo CD as helm-dependency in accordance with the example (https://github.com/argoproj/argocd-example-apps/tree/master/helm-dependency).
Create Chart.yaml
Expected behavior A working installation using ArgoCD
Screenshots