8000 Monocular API - TLS Certificate-Authority Issue · Issue #248 · helm/monocular · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Jul 16, 2021. It is now read-only.
This repository was archived by the owner on Jul 16, 2021. It is now read-only.
Monocular API - TLS Certificate-Authority Issue #248
Open
@andiMenge

Description

@andiMenge

TL;DR
the monocular-api uses the urls found in index.yaml of a chart-repo-server to DownloadAndExtractChartTarball instead of
the one that is configured in api.config.repos.

I have both monocular and my chart-repo-server running in the same k8s cluster and have configured monocular to use the k8s internal service-object to read from the repo. The issue is that the api uses the url from index.yaml to DownloadAndExtractChartTarball. The url that is configured in index.yaml is a ingress url behind a loadbalancer that has self-signed TLS certs.

This results in the following error:

level=error msg="Error on DownloadAndExtractChartTarball" error="Get https://helm-repo-server.example.com/app1-0.2.0.tgz: x509: certificate signed by unknown authority"

In order to fix this I would need a way to insert my self-signed certificate-authority or to force the api-server to use the kubernetes internal http:// address instead of the https:// ingress address it reads from index.yaml.

Is there a way to insert custom ca files or to force the url?

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0