Server IPs blacklisted by opensuse.org about terraform-hcloud-kube-hetzner HOT 5 CLOSED

I think updating the file via github actions would work. But running into rate-limits on download.opensuse.org should not be a common event. Or if it is, it would best fixed upstream by contacting opensuse about it.

So what would think about keeping the original url in the repo and if needed an option to overwrite it locally if needed during development of kube-hetzner itself?

from terraform-hcloud-kube-hetzner.

Yeah, figured the same, it's a rare enough event, tried it and it worked, so the original URL is back. Closing for now!

from terraform-hcloud-kube-hetzner.

We can fetch this file daily with a Github actions workflow, that executes daily or weekly and commits it to the repo, hence completely bypassing the blacklisting potential https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule

The original link is here https://download.opensuse.org/tumbleweed/appliances/openSUSE-MicroOS.x86_64-k3s-kvm-and-xen.qcow2.meta4

from terraform-hcloud-kube-hetzner.

Meaning, the IP had downloaded so much, that it was blacklisted.

This is just a hypothesis, right? Or has it been confirmed in some way? Sounds totally plausible, but it's rather uncommon to just blackhole requests on a dedicated mirror/download server, without at least returning some http error about rate-limiting.
Could it just have been a network hiccup on one specific hcloud server or did it occur multiple times and on different hosts?

from terraform-hcloud-kube-hetzner.

@phaer No it was not the mirrors, all mirrors are in the Github copy of the meta4 files, and work great. It was the MirrorBrain service located at http://download.opensuse.org that was not responding at all. And even opensuse.org or the IP associated with it. So complete ban, probably temporary.

It's also kind of understandable, I must have hit this service quite a few times that day while testing.

from terraform-hcloud-kube-hetzner.