Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rudder can't get my chart #8

Open
Awk34 opened this issue May 11, 2017 · 2 comments
Open

Rudder can't get my chart #8

Awk34 opened this issue May 11, 2017 · 2 comments
Assignees
Labels

Comments

@Awk34
Copy link
Contributor

Awk34 commented May 11, 2017

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
Copy link
Contributor Author

Awk34 commented May 12, 2017

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

@Awk34
Copy link
Contributor Author

Awk34 commented May 17, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants