release icon indicating copy to clipboard operation
release copied to clipboard
verified publisher icon kubernetes

Add file browser for `pkgs.k8s.io`

Open xmudrii opened this issue 2 years ago • 9 comments

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 avatar Oct 11 '23 08:10 xmudrii

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

saschagrunert avatar Oct 11 '23 08:10 saschagrunert

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.

ajinjoseph avatar Nov 06 '23 15:11 ajinjoseph

@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 avatar Nov 06 '23 17:11 xmudrii

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-triage-robot avatar Feb 04 '24 18:02 k8s-triage-robot

/remove-lifecycle stale

xmudrii avatar Feb 06 '24 00:02 xmudrii

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-triage-robot avatar May 06 '24 00:05 k8s-triage-robot

/remove-lifecycle stale

sujoshua avatar May 09 '24 02:05 sujoshua

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-triage-robot avatar Aug 07 '24 02:08 k8s-triage-robot

/lifecycle frozen

xmudrii avatar Aug 07 '24 07:08 xmudrii