search

truecharts / public

Community Helm Chart Repository
https://truecharts.org
GNU Affero General Public License v3.0
1.14k stars 617 forks source link

Your DNS is broken #23475

Closed djjudas21 closed 3 months ago

djjudas21 commented 3 months ago

chart Name

all

Operating System

Talos-OS 1.7

Deployment Method

Helm

Chart Version

999

Kubernetes Events

n/a

chartlication Logs

n/a

Chart Configuration

n/a

Describe the bug

[jonathan@latitude ~]$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "truecharts" chart repository (https://charts.truecharts.org/):
    Get "https://charts.truecharts.org/index.yaml": dial tcp: lookup charts.truecharts.org on 127.0.0.53:53: no such host

Attempting to remove & add truecharts repo

[jonathan@latitude ~]$ helm repo remove truecharts
[jonathan@latitude ~]$ helm repo add truecharts https://charts.truecharts.org/
Error: looks like "https://charts.truecharts.org/" is not a valid chart repository or cannot be reached: Get "https://charts.truecharts.org/index.yaml": dial tcp: lookup charts.truecharts.org on 127.0.0.53:53: no such host

DNS does not resolve on my caching resolver

[jonathan@latitude ~]$ nslookup charts.truecharts.org
Server:     127.0.0.53
Address:    127.0.0.53#53

Non-authoritative answer:
*** Can't find charts.truecharts.org: No answer

DNS does not resolve on Google's nameserver

[jonathan@latitude ~]$ nslookup charts.truecharts.org 8.8.8.8
Server:     8.8.8.8
Address:    8.8.8.8#53

Non-authoritative answer:
*** Can't find charts.truecharts.org: No answer

To Reproduce

n/a

Expected Behavior

n/a

Screenshots

n/a

Additional Context

n/a

I've read and agree with the following

kqmaverick commented 3 months ago

The HTTP Repo was removed. Please see more info on the Discord Announcements

djjudas21 commented 3 months ago

Wow, that's bad form. Not everyone is on Discord 🥴

OCI repos are not as feature-complete as HTTP repos, so this is a degradation in service for many users.

PrivatePuffin commented 3 months ago

Wow, that's bad form. Not everyone is on Discord 🥴

It has to be clearified that we never officially supported using HTTP repos and the guides have been adapted for quite a while as well. So it was not a high-priority announcement, we are/where planning to make a more "full blown" announcement on the website on a later date.

OCI repos are not as feature-complete as HTTP repos, so this is a degradation in service for many users.

Technically the HTTP repo was semi-broken for half a year by now. With versions missing, performance issues, random downtime etcetcetc. It simply is not up-to-the-task of handling our number of Helm Charts. Even worse: It was completely destroying our github api calls, continuesly crashing CIs and so forth./

OCI has been our adviced go-to for quite a few months, we've thoroughly tested it and we've only seen a couple of snags:

I wonder which features you're missing from OCI though?

Our choice was to keep a semi-broken HTTP repo online and have users continue to report errors with it, or take this drastic measure. We've chosen to rather serve less features correctly, than more features inherently broken.

TLDR: The http repo was broken for ages already.

djjudas21 commented 3 months ago

Thanks for the clarification. The feature I am missing is related to how helm chart repos publish their index. Only HTTP repos publish the full index of versions, and this is an important part of my workflow. I'm using Fairwinds Nova to report the difference between deployed charts on my cluster and available charts in the repo - both as a manual command and as a monitoring plugin, so I get a notification when new versions are available. OCI repos don't support this.

I understand as someone who is using TrueCharts via helm on a generic kubernetes cluster, I am not the core user base. But it's still disappointing that you couldn't have put a pinned issue in GitHub or a banner on your docs.

PrivatePuffin commented 3 months ago

OCI repos inherently have an index of all previously published tag... Thats the core of how OCI works...

I think the issue is more with FairWinds Nova being basically out-dated on modern technology if it cannot even do a simple OCI tag lookup... OCI isn't new or anything.

so I get a notification when new versions are available. OCI repos don't support this.

I use Renovate with this just-fine, so it 100% certainly can be done.

I understand as someone who is using TrueCharts via helm on a generic kubernetes cluster, I am not the core user base

Helm users ARE our core userbase.

But it's still disappointing that you couldn't have put a pinned issue in GitHub or a banner on your docs.

You could've also said "thanks if you could expedite that" instead of dwelling that it hasn't happend earlier.

ANyway, locking this, as discussions about the project go on discord and this has turned into a discussion by now