Move to a more reliable chart hosting solution

[max-rocket-internet]

We have periodic problems with chartmuseum running on k8s, e.g:
#606
#554

GHCR has been suggested as a good option.

[pierluigilenoci]

@max-rocket-internet, you have already some PR ready to fix this:
max-rocket-internet/k8s-event-logger#45

[shubhamv1436]

@max-rocket-internet Its still happening. Anything you can do to continuously monitor and automate the fix.

helm repo add deliveryhero https://charts.deliveryhero.io/
Error: looks like "https://charts.deliveryhero.io/" is not a valid chart repository or cannot be reached: failed to fetch https://charts.deliveryhero.io/index.yaml : 504 Gateway Timeout

[msvticket]

Considering that you have Cloudflare configured as CDN in front of the Chartmuseum a quick work around (while working on a long term solution) should be to configure Cloudflare to serve content even though it is stale (i.e. isn't valid according to cache headers).

[bunnybilou]

You might want to consider adding caching on Cloudflare to reduce the need for frequent origin fetches.

I checked the Argo Helm repository, and they have a max-age of 600 seconds configured for caching: https://argoproj.github.io/argo-helm/index.yaml

[max-rocket-internet]

a quick work around (while working on a long term solution) should be to configure Cloudflare to serve content even though it is stale
You might want to consider adding caching on Cloudflare to reduce the need for frequent origin fetches.

Good ideas @bunnybilou @msvticket, I've added this rule for now:

@max-rocket-internet, you have already some PR ready to fix this:
max-rocket-internet/k8s-event-logger#45

Thanks but this PR is for Github pages, which we won't do.

We will use use GHCR, I just need to find some time to setup up the CI, hopefully I can do it this week or early next, in the mean time the Cloudflare cache rule should work 🙏

[max-rocket-internet]

I would be grateful if everyone could take a look at this PR 😄