Skip to content
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

Closed
arschles opened this issue Oct 25, 2021 · 5 comments
Closed

Container registry page for KEDA is 404ing #2215

arschles opened this issue Oct 25, 2021 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@arschles
Copy link
Contributor

arschles commented Oct 25, 2021

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

  1. Log out of GitHub or enter a private browsing window (i.e. incognito on Chrome)
  2. Go to https://github.com/kedacore/keda/pkgs/container/keda
  3. Observe that the page 404s

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.

@tomkerkhove
Copy link
Member

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.

@arschles
Copy link
Contributor Author

this is a GitHub UI thing rather than something we can configure

@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.

Let me ask around.

Thanks! I'm happy to do so if you'd like, just let me know.

@stale
Copy link

stale bot commented Dec 25, 2021

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.

@stale stale bot added the stale All issues that are marked as stale due to inactivity label Dec 25, 2021
@tomkerkhove tomkerkhove self-assigned this Dec 25, 2021
@stale stale bot removed the stale All issues that are marked as stale due to inactivity label Dec 25, 2021
@tomkerkhove
Copy link
Member

It looks like this is no longer the case, can you verify please @arschles?

@arschles
Copy link
Contributor Author

Yup, looks like it's fine now. I checked the kedacore/keda package as well as the http-add-on interceptor package. Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants