Skip to content

Commit

Permalink
Note for v1.2.2 upgrades (#627)
Browse files Browse the repository at this point in the history 
* note to label secret

Co-authored-by: Jillian <67180770+jillian-maroket@users.noreply.github.com>
  • Loading branch information
@ibrokethecloud @jillian-maroket
ibrokethecloud and jillian-maroket authored Aug 22, 2024
1 parent 6027f71 commit 623da80
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 0 deletions.
5 changes: 5 additions & 0 deletions docs/upgrade/v1-2-2-to-v1-3-1.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,11 @@ For air-gapped environments, see [Prepare an air-gapped upgrade](./automatic.md#

### 1. Cluster upgrade stuck after the first node is upgraded

:::tip
To prevent this issue from occurring, label the `local-kubeconfig` secret before starting the upgrade process.
`kubectl label secret local-kubeconfig -n fleet-local cluster.x-k8s.io/cluster-name=local`
:::

When upgrading a Harvester cluster from v1.2.2 or v1.3.0 to v1.3.1, the upgrade process becomes stuck after the first node is upgraded.

Example:
Expand Down
5 changes: 5 additions & 0 deletions versioned_docs/version-v1.3/upgrade/v1-2-2-to-v1-3-1.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,11 @@ For air-gapped environments, see [Prepare an air-gapped upgrade](./automatic.md#

### 1. Cluster upgrade stuck after the first node is upgraded

:::tip
To prevent this issue from occurring, label the `local-kubeconfig` secret before starting the upgrade process.
`kubectl label secret local-kubeconfig -n fleet-local cluster.x-k8s.io/cluster-name=local`
:::

When upgrading a Harvester cluster from v1.2.2 or v1.3.0 to v1.3.1, the upgrade process becomes stuck after the first node is upgraded.

Example:
Expand Down

0 comments on commit 623da80

Please sign in to comment.