-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Helm operator: dependency failure #1852
Comments
ETA? |
Yes. Thx
|
|
@hiddeco See above errors. Do I also need to update the flux operator at the same time? |
Is the custom resource listed under |
I did a full reinstall and got this.
|
@hiddeco Note that the first line is the original error that I reported. |
Here is my
|
Ah, that’s some unexpected bad news 😔
But thanks for the `requirements.yaml`, that should be enough for me to try
to replicate the issue. I am off for today but will do first thing tomorrow
morning.
Is it correct to assume the chart in your `HelmRelease` is running from a
git source?
…On Thu, 21 Mar 2019 at 20:05, Derrick Burns ***@***.***> wrote:
Here is my requirements.yaml file.
dependencies:
- name: gloo
repository: https://storage.googleapis.com/solo-public-helm/
version: 0.10.5
condition: gloo.enabled
tags:
- front-end
- name: ambassador
repository: https://kubernetes-charts.storage.googleapis.com/
version: 1.1.5
condition: ambassador.enabled
tags:
- front-end
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1852 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJmMvx9SaDrrrMMunzXzesm7qi63u1yQks5vY9gKgaJpZM4cCDcd>
.
|
Yes. Thx!
|
This ends up not being the problem, you should add the repositories from your Details about how and where to mount a custom |
Closing this as it has been superseded by #1862. |
It appears that the helm operator does not handle dependencies whose repo ends in a slash,such as when using a sub-repo in the google repo such as solo-public-repo.
Using an independent HelmRelease for the dependency works.
Using helm directly works.
Using weave helm operator with a dependency as described does not work.
The text was updated successfully, but these errors were encountered: