kanisterio / kanister-charts

Github pages endpoint to host kanister helm charts index
0 stars 0 forks source link

Several chart tarballs unavailable #1

Open wesjdj opened 2 weeks ago

wesjdj commented 2 weeks ago

Hi,

Since earlier today, I have been unable to pull several charts.

helm show chart kanister/profile
Error: failed to fetch https://charts.kanister.io/profile-0.111.0.tgz : 404 Not Found
helm show chart kanister/kanister-postgresql
Error: failed to fetch https://charts.kanister.io/kanister-postgresql-0.32.0.tgz : 404 Not Found
helm show chart kanister/kanister-mysql
Error: failed to fetch https://charts.kanister.io/kanister-mysql-0.32.0.tgz : 404 Not Found

kanister-operator, however, is available.

helm show chart kanister/kanister-operator
apiVersion: v1
appVersion: 0.112.0
description: Kanister-operator Helm chart for Kubernetes
home: https://kanister.io/
icon: https://kasten.io/assets/img/kanister-logo.png
maintainers:
- email: ilya@kasten.io
  name: depohmel
- email: tom@kasten.io
  name: tdmanv
name: kanister-operator
version: 0.112.0

I have seen some activity in this repo yesterday, could this have caused these issues?

Thanks

viveksinghggits commented 2 weeks ago

Hi @wesjdj , Thank you for reporting this. Yes we did change how/where the helm chart was being hosted and that might have caused this.

On the other hand, do you really need the other helm charts? You don't need kanister/profile helm chart for sure, profiles are K8s custom resources (introduced by Kanister) that can be created like any other K8s resource.

And for kanister-postgresql and kanister-mysql, are you just trying to install postgresql and mysql, can you install them from respective helm charts?

wesjdj commented 2 weeks ago

Thanks for your reply @viveksinghggits

We currently use the kanister/profile chart. We use FluxCD for GitOps, which uses its own flavour of Kustomize. When Flux Kustomize applies resources, it prioritises CRDs, followed by CRs, followed by other resources, including Helm releases.

This means that we first install the blueprints & profiles CRDs, followed by the profile CR (using the kanister/profile chart), followed by the kanister/kanister-operator Helm release (with controller.updateCRDs = false).

It has been a couple of years since I set up our pipeline to install and configure Kanister, but at the time, this was the only way I could get it to work with our GitOps setup.

I could modify the setup to install the profile CR without the chart, but it begs the question of why the chart is available in the Kanister Helm repo if you don't think there is a purpose for it?

Either way, I'm pretty certain that the kanister/profile chart is unavailable due to the recent changes made in this repo.

viveksinghggits commented 2 weeks ago

Either way, I'm pretty certain that the kanister/profile chart is unavailable due to the recent changes made in this repo.

I agree with the point that the helm chart is not available because of the recent changes. And if you want, we would obviously make it available there at the new location.

What I am trying to share is, the helm chart just for profile should not be needed. We should be able to create the profile by applying the k8s profile resource manifest. I am not sure if looked into that helm chart but it just creates a profile resource and a secret which can very easily be done without using the helm chart. But like I said if you still think that it would not work for you we can discuss the detailed used case and decide if we need to publish the profile helm chart as well.