Add a landing page for pkgs.k8s.io

[xmudrii]

What would you like to be added:

Relevant to #3317

We should have a landing page at pkgs.k8s.io that shows:

• basic information about the new package repositories
• information about the new package repositories replacing the legacy repositories
• guarantees that we do or don't provide for these repositories

Also see kubernetes/k8s.io#6188 (comment)

[saschagrunert]

Would it be enough to link to an existing or new section/page on https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/#installing-kubeadm-kubelet-and-kubectl ?

[xmudrii]

@saschagrunert I'd prefer something like registry.k8s.io (https://github.com/kubernetes/registry.k8s.io)

[xmudrii]

Implemented a temporary workaround to redirect to the announcement blog post in kubernetes/k8s.io#6544
I'll keep this issue open to try to figure out if we can come up with a better landing page

[saschagrunert]

@xmudrii I'd generally prefer integrating the landing page into something we already maintain compared to a separated resource we may forget.

[ocaner-biz]

I'm currently trying to upgrade my local labs cluster from v1.29 to v1.30 but I'm facing issues to figure out the correct url for the repository.

After googling and cross reading many blog posts I've found out that prereleases are available using the following repository url for debian/ubuntu:

https://pkgs.k8s.io/core:/prerelease:/v1.30/deb/

A landing page containing information about all releases would be very handy.

[xmudrii]

I thought about adding a new folder to k/sig-release (e.g. pkgs.k8s.io) that's going to hold the user-facing documentation for the new package repositories, and then we use README in that directory as the landing page. However, before we do that, I'd like to coordinate these efforts with #3317

[k8s-triage-robot]

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