Skip to content

Commit e3c1c5b

Browse files
author
Tim Bannister
committed
Redo advice about cluster upgrades
Use one consistent phrase about the advice around upgrading a cluster.
1 parent 2b29735 commit e3c1c5b

File tree

3 files changed

+13
-4
lines changed

3 files changed

+13
-4
lines changed

content/en/docs/tasks/administer-cluster/cluster-upgrade.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,10 @@ weight: 350
88
This page provides an overview of the steps you should follow to upgrade a
99
Kubernetes cluster.
1010

11+
The Kubernetes project recommends upgrading to the latest patch releases promptly, and
12+
to ensure that you are running a supported minor release of Kubernetes.
13+
Following this recommendation helps you to to stay secure.
14+
1115
The way that you upgrade a cluster depends on how you initially deployed it
1216
and on any subsequent changes.
1317

content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,11 @@ Client certificates generated by [kubeadm](/docs/reference/setup-tools/kubeadm/)
1414
This page explains how to manage certificate renewals with kubeadm. It also covers other tasks related
1515
to kubeadm certificate management.
1616

17+
The Kubernetes project recommends upgrading to the latest patch releases promptly, and
18+
to ensure that you are running a supported minor release of Kubernetes.
19+
Following this recommendation helps you to to stay secure.
20+
21+
1722
## {{% heading "prerequisites" %}}
1823

1924

@@ -165,10 +170,6 @@ if you don't have specific requirements on certificate renewal and perform Kuber
165170
upgrades regularly (less than 1 year in between each upgrade), kubeadm will take care of keeping
166171
your cluster up to date and reasonably secure.
167172
168-
{{< note >}}
169-
It is a best practice to upgrade your cluster frequently in order to stay secure.
170-
{{< /note >}}
171-
172173
If you have more complex requirements for certificate renewal, you can opt out from the default
173174
behavior by passing `--certificate-renewal=false` to `kubeadm upgrade apply` or to `kubeadm
174175
upgrade node`.

content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,10 @@ please refer to following pages instead:
2121
- [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -4 >}} to {{< skew currentVersionAddMinor -3 >}}](https://v{{< skew currentVersionAddMinor -3 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)
2222
- [Upgrading a kubeadm cluster from {{< skew currentVersionAddMinor -5 >}} to {{< skew currentVersionAddMinor -4 >}}](https://v{{< skew currentVersionAddMinor -4 "-" >}}.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)
2323

24+
The Kubernetes project recommends upgrading to the latest patch releases promptly, and
25+
to ensure that you are running a supported minor release of Kubernetes.
26+
Following this recommendation helps you to to stay secure.
27+
2428
The upgrade workflow at high level is the following:
2529

2630
1. Upgrade a primary control plane node.

0 commit comments

Comments
 (0)