Add advice about checking package repository source (RPM)

[rotimislaw]

Description

I spent lots of time trying to upgrade my Kubernetes cluster and re-reading the official doc only to realise the information I was missing wasn't referenced in the main kubeadm upgrade document, but one of the subsequent pages. I believe simple reference in correct place will facilitate upgrade process for many people doing this from now on

Issue

N/A

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: rotimislaw / name: Robert Matuszewski (7d7a391, 1bbff5c, 05f862d, 73a4126)

[k8s-ci-robot]

Welcome @rotimislaw!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	73a4126
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/67239bbba7c9270008d51e99
😎 Deploy Preview	https://deploy-preview-48608--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.

[neolit123]

having this note seems ok. made one suggestion.

/sig cluster-lifecycle

[neolit123]

/tide merge-method-squash
/lgtm
/assign @nate-double-u

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from nate-double-u. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• content/en/docs/OWNERS

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

[neolit123]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: e944e0a398c9022ae904f071692b5961edaadba7

[sftim]

/retitle Add advice about checking package repository source (RPM)

[tengqm]

I'd suggest we put this a little bit earlier in this page, something like the following
as a precondition to check.

Suggested change

	If you don't see the version you expect to upgrade to, [verify if the Kubernetes package repositories are used.](/docs/tasks/administer-cluster/kubeadm/change-package-repository/#verifying-if-the-kubernetes-package-repositories-are-used)
	Please make sure you are using [the Kubernetes package repositories](/docs/tasks/administer-cluster/kubeadm/change-package-repository/#verifying-if-the-kubernetes-package-repositories-are-used)
	when upgrading a cluster.

[rotimislaw]

Thanks for your input @tengqm ! The case is there's a similar reference to what you say just above the section where I want to include this comment. I was wondering if it won't be better to just rephrase that one, because for me (quite newby in Kubernetes) it wasn't straightforward connection I should change the package repository to be able to download other Kubernetes version. Thus I believe it's important to include the 'version' keyword in this context, nonetheless of where it would be

What do you think?

[tengqm]

My take was that if you are not using the official package repository, you may encounter problems other than versions missing. I was suggesting to make this as early as possible in this page, and to avoid restricting the problem to the version issue.