Update package manager instructions with community-hosted repos

[xmudrii]

This PR documents usage of the community-hosted repositories, implemented as part of KEP-1731.

All documents that mention the deprecated Google-hosted repository are updated to:

• Highlight that the Google-hosted repository is deprecated and that using the community-hosted repositories is strongly recommended
• Highlight the most important differences between the Google-hosted repository and the community-hosted repositories
• Show how to setup both the community-hosted repositories and the Google-hosted repository

I decided to go with Google-hosted repository and Community-hosted repositories for wording to distinct between repositories hosted on Google and our infra.

It's important to note that the infrastructure and repositories, and the KEP, don't have the same graduation criteria. We consider the infrastructure and repositories to be GA, but the KEP itself is graduating to alpha. That's because KEP covers more than the infrastructure and repositories and those tasks are still to be done in the upcoming release cycles.

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	be65d00
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/64b11f1400329a0008b0b4d9
😎 Deploy Preview	https://deploy-preview-42022--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

Name	Link
🔨 Latest commit
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/64d5e9ca8e0cde3bbaaa232c

[xmudrii]

@kubernetes/sig-release-leads @kubernetes/release-engineering @sftim I'm looking for some initial feedback on structure and wording. I'll work on the document explaining community-hosted repositories tomorrow.

[jeremyrickard]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 592bcdd987f0dd62a93d756fe75c55ad39cd03f7

[sftim]

/hold cancel

[sftim]

/lgtm
/approve

I'll send in a PR to revert the last commit here.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 06958f167a7cd405dd59d6d8a5184405744bcd69

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sftim

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• content/en/OWNERS [sftim]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sftim]

This tested fine previously, but Netlify hasn't updated the PR status to match.

[sftim]

Helps with #42810

[torenware]

PLEASE CONSIDER ROLLING THIS BACK. Seriously. You're screwing up the ability of users to install anything other than for v1.28, WHICH NEEDS TO BE DOCUMENTED IN THE CURRENT PAGE.

This is a screw-up, very simply.

[cpanato]

PLEASE CONSIDER ROLLING THIS BACK. Seriously. You're screwing up the ability of users to install anything other than for v1.28, WHICH NEEDS TO BE DOCUMENTED IN THE CURRENT PAGE.

This is a screw-up, very simply.

Please be more kind and respectful. If that breaks something on your end, let us know in a better way not using this type of language; most people here do this in their free time.