rudder icon indicating copy to clipboard operation
rudder copied to clipboard

Rudder can't get my chart

Open Awk34 opened this issue 7 years ago • 2 comments

I have a chart repo being served from S3. I can grab the chart packages and index.yaml file fine through GET requests. I have the repo configured for Rudder in my ConfigMap. I can successfully list my charts with a GET on https://rudder.mysite.com/api/v1/repo/my-repo/charts.

When I try to POST to https://rudder.mysite.com/api/v1/releases with the following body, I get the following error:

{
    name: 'test',
    namespace: 'test',
    repo: 'my-repo',
    chart: 'my-chart',
    version: '1.0.2',
    values: {
        key: 'value',
    }
}
Unable to get chart from cache or my-chart-1.0.2.tgz" error="Get my-chart-1.0.2.tgz: unsupported protocol scheme \"\"
unable to get chart details" error="Get my-chart-1.0.2.tgz: unsupported protocol scheme \"\"
unable to install releases" error="[ServiceError:500] unable to install releases

Awk34 avatar May 11 '17 22:05 Awk34

Do you guys need any more info? I can set up a public S3 charts repo if you need as well.

Awk34 avatar May 12 '17 18:05 Awk34

Good news! This isn't an issue with rudder.

The issue was that I was indexing my charts repo with helm repo index ., whereas I should have been using helm repo index --url http://my-repo.s3-website-us-east-1.amazonaws.com/charts . This isn't documented all too well (the specific error isn't referenced anywhere in the Helm docs). I'm adding a FAQ doc about it.

Anywho, this error should probably produce a 400 level error from rudder instead of a 500.

Awk34 avatar May 17 '17 19:05 Awk34