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

Add file browser for pkgs.k8s.io #3317

Open
xmudrii opened this issue Oct 11, 2023 · 9 comments
Open

Add file browser for pkgs.k8s.io #3317

xmudrii opened this issue Oct 11, 2023 · 9 comments
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@xmudrii
Copy link
Member

xmudrii commented Oct 11, 2023

What would you like to be added:

The legacy package repositories (and most of package repositories) supported browsing files, e.g. you can browser the APT repository by going over to apt.kubernetes.io. This is however not the case for pkgs.k8s.io because the underlying S3 bucket is private and pkgs.k8s.io points to a CDN.

We should research if it's possible to have a file browser in front of pkgs.k8s.io that would allow users to check contents of our repositories.

If this is not possible, we should at least try to avoid throwing 403 Forbidden when trying to access URLs of directories (e.g. https://pkgs.k8s.io/core:/stable:/v1.28/deb) because this is confusing for users (see #3219).

/priority backlog

@xmudrii xmudrii added kind/feature Categorizes issue or PR as related to a new feature. sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Oct 11, 2023
@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Oct 11, 2023
@xmudrii xmudrii moved this to 🔖 Backlog in SIG Release - Packaging Oct 11, 2023
@saschagrunert
Copy link
Member

We have at least something like this as browsable interface: https://download.opensuse.org/repositories/isv:/kubernetes:/core:/stable:/

@ajinjoseph
Copy link

Hi ,

Is there any update on this issue ? I am still facing errors as below

root@node01 ~ ➜ sudo apt-get updateHit:2 https://download.docker.com/linux/ubuntu focal InRelease
Hit:3 http://archive.ubuntu.com/ubuntu focal InRelease
Hit:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Err:1 https://prod-cdn.packages.k8s.io/repositories/isv:/kubernetes:/core:/stable:/v1.27.0-00/deb InRelease
403 Forbidden [IP: 18.172.122.38 443]
Hit:6 http://security.ubuntu.com/ubuntu focal-security InRelease
Reading package lists... Done
E: Failed to fetch https://pkgs.k8s.io/core:/stable:/v1.27.0-00/deb/InRelease 403 Forbidden [IP: 18.172.122.38 443]
E: The repository 'https://pkgs.k8s.io/core:/stable:/v1.27.0-00/deb InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

@xmudrii
Copy link
Member Author

xmudrii commented Nov 6, 2023

@ajinjoseph Looks like your repo is not configured correctly, you shouldn't have v1.27.0-00, it should be only v1.27.0. Please follow the official installation guide to configure repositories.

@xmudrii xmudrii moved this from 🔖 Backlog to Backlog (prioritized) in SIG Release - Packaging Nov 12, 2023
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 4, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Feb 6, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 6, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 6, 2024
@sujoshua
Copy link

sujoshua commented May 9, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 9, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 7, 2024
@xmudrii
Copy link
Member Author

xmudrii commented Aug 7, 2024

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
Status: Backlog (prioritized)
Development

No branches or pull requests

6 participants