-
Notifications
You must be signed in to change notification settings - Fork 807
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
https://pkgs.k8s.io/ does not support ipv6 #6820
Comments
This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
I have found out that myth curl was trying to send an IPv6 request... Which means that Mean while, I had to do this to solve my issue.
|
@Martin-Luther Thank you for raising the issue. But here I had tried but it is not triggering such error. Can you Please check Which Ubuntu and deb you are using if you are using older than Debian 12 and Ubuntu 22.04, then you manually need to make directory using If you satisfied all these criteria and still you are facing an issue then check if your network might have a firewall or proxy that is blocking the request so disable it. else check whether you entered the correct url. |
/kind support |
The issue was solved by forcing curl, apt-get & wget to use ipv4 because my system is ipv6 by default. I am using Debian 12
|
/retitle https://pkgs.k8s.io/ does not support ipv6 |
moving this to k8s.io for triage, seems like the ipv6 problem should be checked |
/sig release |
cc @xmudrii |
Hello, |
@Martin-Luther What cloud provider are you using? We have been observing blocked IP addresses from Hetzner; are you using Hetzner by any chance? |
As mentioned in my previous message :
I am @ Gandi, and seriously thinking about moving to Digital Ocean or Hostinger if they allow me o add additional volumes ... |
pkgs.k8s.io is currently hosted with a combination of GCP + AWS (like most, but not all of our infra), we have to work with what is available to us and major cloud providers do block some IPs for various reasons (e.g. US sanctions, abuse, ...). If someone wanted to help provide a mirror, we could consider it, otherwise I recommend self-hosting a personal mirror (or obtaining hosting without IP reputation issues, or escalating to your hosting provider), it simply isn't scalable for us to follow up on these as a project and we don't have a viable alternative on hand for hosting, these vendors are providing a lot of resources to the project. It seems the title of this issue is inaccurate? |
Tested on an AWS EC2 instance with IPv6 address and no public IPv4 address, works perfectly fine. Packages are installed without a problem, and I can see that the IPv6 address is used if curl Given that we have IPv6 support, I'm going to close this issue. |
@xmudrii: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
The following command generates
curl: (22) The requested URL returned error: 403
The text was updated successfully, but these errors were encountered: