From b2956d567fe6616061eca95b63435c5431eb7cf7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nick=20J=C3=BCttner?= Date: Thu, 12 Dec 2024 13:11:42 +0100 Subject: [PATCH 1/3] add workload cluster upgrade section --- .../manage-workload-clusters/index.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md b/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md index 456f48186c..9a781e4941 100644 --- a/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md +++ b/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md @@ -227,6 +227,21 @@ The command will create the folders and the files needed. If you already applied Alternatively, you can add the flag `--cluster-user-config` with the values you want to add to the cluster and it will generate a `ConfigMap` with the values. +#### Upgrading workload clusters + +To upgrade a workload cluster, you need to change the `release.version` field in the user config file. After that, you commit and push the changes to the repository. The `Flux` controller will detect the changes and the cluster will be upgraded to the new version. The release version can be found by running `kubectl get releases` in the management cluster. You only need to set the semver version in the `release.version` field. + +Example: + +`kubectl get releases`: + +```sh +NAME KUBERNETES VERSION FLATCAR VERSION AGE STATE +aws-29.4.0 1.29.10 3975.2.2 29d active +``` + +You set the `release.version` in the `cluster-user-config` file to `29.4.0` and commit and push the changes. + ### Installing managed apps Installing applications is easy now that you have the GitOps structure in place. In this tutorial you are going to install `Grafana` to understand the process. From dc2db0852279832785ceabe5c83e6ac2775ad48a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nick=20J=C3=BCttner?= Date: Thu, 12 Dec 2024 13:17:14 +0100 Subject: [PATCH 2/3] add workload cluster upgrade section --- .../continuous-deployment/manage-workload-clusters/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md b/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md index 9a781e4941..c5e63b1f7c 100644 --- a/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md +++ b/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md @@ -13,7 +13,7 @@ user_questions: - How to ensure security by combining Flux with the platform API permission model? owner: - https://github.com/orgs/giantswarm/teams/team-honeybadger -last_review_date: 2024-11-11 +last_review_date: 2024-12-12 --- Below you will learn how to manage infrastructure and applications in the Giant Swarm `Flux` setup. @@ -229,7 +229,7 @@ Alternatively, you can add the flag `--cluster-user-config` with the values you #### Upgrading workload clusters -To upgrade a workload cluster, you need to change the `release.version` field in the user config file. After that, you commit and push the changes to the repository. The `Flux` controller will detect the changes and the cluster will be upgraded to the new version. The release version can be found by running `kubectl get releases` in the management cluster. You only need to set the semver version in the `release.version` field. +To upgrade a workload cluster, you need to change the `release.version` field in the `cluster-user-config` file. After that, you commit and push the changes to the repository. The `Flux` controller will detect the changes and the cluster will be upgraded to the new version. The release version can be found by running `kubectl get releases` in the management cluster. You only need to set the version in the `release.version` field. Example: From d1f11bafc7d877468dacc3b89c11c6e60bff00fe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nick=20J=C3=BCttner?= Date: Thu, 12 Dec 2024 13:21:51 +0100 Subject: [PATCH 3/3] trailing --- .../continuous-deployment/manage-workload-clusters/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md b/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md index c5e63b1f7c..bf451f591c 100644 --- a/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md +++ b/src/content/tutorials/continuous-deployment/manage-workload-clusters/index.md @@ -231,7 +231,7 @@ Alternatively, you can add the flag `--cluster-user-config` with the values you To upgrade a workload cluster, you need to change the `release.version` field in the `cluster-user-config` file. After that, you commit and push the changes to the repository. The `Flux` controller will detect the changes and the cluster will be upgraded to the new version. The release version can be found by running `kubectl get releases` in the management cluster. You only need to set the version in the `release.version` field. -Example: +Example: `kubectl get releases`: