Use sudo for elevated permissions while upgrading clusters using kubeadm

[adityasamant25]

The pages for Upgrading kubeadm clusters and Upgrading Linux nodes have reference to apt, apt-cache, apt-mark, apt-get, yum and kubeadm upgrade apply commands. These commands need elevated permissions through sudo (if executed without root).

The PR adds the usage of sudo for these commands to ease the experience for the reader.

Regards,
Aditya

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	c6e210f
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/65b0e0692a53c3000883ccd6
😎 Deploy Preview	https://deploy-preview-44832--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.

[T-Lakshmi]

I think its worth to mention sudo.
Looking good to me

Preview page:
Upgrading Linux nodes | Upgrading kubeadm clusters

[neolit123]

are these all the commands that need sudo on the pages?
/lgtm

but leaving to SIG docs what needs to be done here.
we had a discussion before that the sudo requirement can be just a note on top of the doc instead of having sudo on every command.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b9a5565de5441af669e9fc62f1b04b05918d16af

[neolit123]

/sig cluster-lifecycle

[adityasamant25]

are these all the commands that need sudo on the pages? /lgtm

I have executed the steps on this page several times. I am pretty confident that all commands that need sudo have been taken care of in this PR.

[T-Lakshmi]

we had a discussion before that the sudo requirement can be just a note on top of the doc instead of having sudo on every command.

Good suggestion,
I believe this approach is an efficient way of documenting.

[adityasamant25]

I believe most readers would copy paste the commands. And it is an inconvenience to re-execute with sudo each time a command fails with permissions. Some commands on the page already had the sudo prefixed. This PR adds it to the missing ones.

[sftim]

(nit)
I'd have put this fixup in a separate commit.

[sftim]

Consider mentioning sudo in the prerequisites, and ideally tell people that alternative tools work fine.

(I like using PolicyKit locally, and sometimes use alternatives to sudo on servers).

Anyway:
/approve

[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