This message was deleted.

sparse-intern-71089

12/29/2019, 5:14 AM

This message was deleted.

white-balloon-205

12/29/2019, 5:18 AM

What is the full error you get? Or more specifically - in what way does

helm fetch gloo/gloo --untar --destination /tmp/tmp-12397xMcptBYcaXX7

fail? Note that that is just about fetching the chart - none of the actual Helm semantics should be involved? I suspect this is not related to Helm 2 vs. Helm 3 (curious if there was a specific reason you expected it was?)

rhythmic-hair-33677

12/29/2019, 5:19 AM

repo gloo not found

white-balloon-205

12/29/2019, 5:20 AM

Okay - have you not run these commands yet locally?

Copy code

helm repo add gloo <https://storage.googleapis.com/solo-public-helm>
helm repo update

rhythmic-hair-33677

12/29/2019, 5:21 AM

No 🤦

white-balloon-205

12/29/2019, 5:22 AM

Note that I believe it is possible to provide this directly to teh

Chart

constructor without needing to run the commands locally - but I can't off the top of my head recall the incantations.

rhythmic-hair-33677

12/29/2019, 5:27 AM

Oh that is interesting. Right now I have a bootstrap.sh for the

helm repo add

things. No clue why I assumed this one wouldn’t need it.

glamorous-printer-66548

12/29/2019, 10:40 AM

you can pass the fully qualified chart URL to the constructor instead of the chart and repo name. Then you don't have to run Helm repo add before.

🎄 1

👍 1

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.