You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to deploy a helm chart into my vCluster, but vCluster was logging the error:
ERROR deploy/start.go:42 Error deploying manifests: couldn't find chart {"component": "vcluster"}
What did you expect to happen?
vCluster installs the specified helm chart.
How can we reproduce it (as minimally and precisely as possible)?
vCluster will download and store the chart in its working directory as strimzi-kafka-operator-helm-3-chart-0.41.0.tgz.
Then it will fail with the error I mentioned. If I manually enter the vCluster pod and rename the file to strimzi-kafka-operator-0.41.0.tgz, it continues and succeeds.
This is because it only works, if the downloaded artefact name equals the specified helm chart name. I checked your code and this seems to be the issue.
What happened?
I wanted to deploy a helm chart into my vCluster, but vCluster was logging the error:
ERROR deploy/start.go:42 Error deploying manifests: couldn't find chart {"component": "vcluster"}
What did you expect to happen?
vCluster installs the specified helm chart.
How can we reproduce it (as minimally and precisely as possible)?
Specify a helm release like this:
...
name: strimzi-kafka-operator
repo: https://strimzi.io/charts
version: "0.41.0"
...
vCluster will download and store the chart in its working directory as strimzi-kafka-operator-helm-3-chart-0.41.0.tgz.
Then it will fail with the error I mentioned. If I manually enter the vCluster pod and rename the file to strimzi-kafka-operator-0.41.0.tgz, it continues and succeeds.
This is because it only works, if the downloaded artefact name equals the specified helm chart name. I checked your code and this seems to be the issue.
Anything else we need to know?
No response
Host cluster Kubernetes version
vcluster version
VCluster Config
The text was updated successfully, but these errors were encountered: