-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Container registry page for KEDA is 404ing #2215
Comments
From what I'm seeing this is a GitHub UI thing rather than something we can configure as all the images are public and pull just fine. Let me ask around. |
@tomkerkhove agreed. the issue came up because the link checker in the HTTP Addon was failing. I had an assumption that those GH Container Registry pages would be publicly accessible, but if that needs to change I'm happy to do so.
Thanks! I'm happy to do so if you'd like, just let me know. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
It looks like this is no longer the case, can you verify please @arschles? |
Yup, looks like it's fine now. I checked the |
Report
When I go to https://github.com/kedacore/keda/pkgs/container/keda, I get a 404 page when I am not logged into GitHub (i.e. in a private browsing window)
Expected Behavior
The page does not 404
Actual Behavior
The page 404s. The correct behavior exhibits when I am logged into GitHub
Steps to Reproduce the Problem
Logs from KEDA operator
N/A
KEDA Version
2.4.0
Kubernetes Version
No response
Platform
No response
Scaler Details
No response
Anything else?
This issue is not related to the KEDA software itself. Rather, it's related to project infrastructure. Note that the same issue is occurring with the HTTP Addon images: interceptor, operator and scaler. I suspect these are misconfigured as well, but I don't see anything wrong with the settings - they all are set to public visibility.
The text was updated successfully, but these errors were encountered: