From a466564212c4816a7ac5dffd9be29fcf84608b24 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nick=20J=C3=BCttner?= Date: Thu, 21 Nov 2024 13:11:55 +0100 Subject: [PATCH] fix missing field for release version (#1506) --- azure/v25.0.0/README.md | 2 +- cloud-director/v27.0.0/README.md | 4 ++-- vsphere/v27.0.0/README.md | 4 ++-- vsphere/v27.0.1/README.md | 4 ++-- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/azure/v25.0.0/README.md b/azure/v25.0.0/README.md index 4ed95bafe..d61dfc4a5 100644 --- a/azure/v25.0.0/README.md +++ b/azure/v25.0.0/README.md @@ -6,7 +6,7 @@ We are happy to announce the first release for Azure that uses the new release f In order to consume the new flow, the following two fields need to be manually adapted: -* In ConfigMap `-userconfig` set `.Values.global.release` to the release version, e.g. `25.0.0`. +* In ConfigMap `-userconfig` set `.Values.global.release.version` to the release version, e.g. `25.0.0`. * In App `` remove the `spec.version` field. In case of GitOps, Flux might complain that the app manifest is invalid as the `spec.version` field is mandatory. In that case, edit the live App CR and set `spec.version` to an empty string. That will unblock Flux and allow it reconcile successfully. And if you want to use `kubectl-gs` to create a cluster, you'd need to now specify the release version, e.g.: diff --git a/cloud-director/v27.0.0/README.md b/cloud-director/v27.0.0/README.md index a39cba9c2..38b65efe6 100644 --- a/cloud-director/v27.0.0/README.md +++ b/cloud-director/v27.0.0/README.md @@ -6,11 +6,11 @@ We are happy to announce the first release for VMware Cloud Director that uses t In order to consume the new flow, the following two fields need to be manually adapted: -* In ConfigMap `-userconfig` set `.Values.global.release` to the release version, e.g. `27.0.0`. +* In ConfigMap `-userconfig` set `.Values.global.release.version` to the release version, e.g. `27.0.0`. * In App `` remove the `spec.version` field. In case of GitOps, Flux might complain that the app manifest is invalid as the `spec.version` field is mandatory. In that case, edit the live App CR and set `spec.version` to an empty string. That will unblock Flux and allow it reconcile successfully. And if you want to use `kubectl-gs` to create a cluster, you'd need to now specify the release version, e.g.: ```bash -kubectl-gs template cluster --provider cloud-director --organization my_org --name cluster_name --release v27.0.0 +kubectl-gs template cluster --provider cloud-director --organization my_org --name cluster_name --release 27.0.0 ``` diff --git a/vsphere/v27.0.0/README.md b/vsphere/v27.0.0/README.md index 39ceda750..ccf073a85 100644 --- a/vsphere/v27.0.0/README.md +++ b/vsphere/v27.0.0/README.md @@ -6,11 +6,11 @@ We are happy to announce the first release for vSphere that uses the new release In order to consume the new flow, the following two fields need to be manually adapted: -* In ConfigMap `-userconfig` set `.Values.global.release` to the release version, e.g. `27.0.0`. +* In ConfigMap `-userconfig` set `.Values.global.release.version` to the release version, e.g. `27.0.0`. * In App `` remove the `spec.version` field. In case of GitOps, Flux might complain that the app manifest is invalid as the `spec.version` field is mandatory. In that case, edit the live App CR and set `spec.version` to an empty string. That will unblock Flux and allow it reconcile successfully. And if you want to use `kubectl-gs` to create a cluster, you'd need to now specify the release version, e.g.: ```bash -kubectl-gs template cluster --provider vsphere --organization my_org --name cluster_name -vsphere-network-name network_name --release v27.0.0 +kubectl-gs template cluster --provider vsphere --organization my_org --name cluster_name -vsphere-network-name network_name --release 27.0.0 ``` diff --git a/vsphere/v27.0.1/README.md b/vsphere/v27.0.1/README.md index c45999696..bf7794670 100644 --- a/vsphere/v27.0.1/README.md +++ b/vsphere/v27.0.1/README.md @@ -6,11 +6,11 @@ We are happy to announce the first release for vSphere that uses the new release In order to consume the new flow, the following two fields need to be manually adapted: -* In ConfigMap `-userconfig` set `.Values.global.release` to the release version, e.g. `27.0.1`. +* In ConfigMap `-userconfig` set `.Values.global.release.version` to the release version, e.g. `27.0.1`. * In App `` remove the `spec.version` field. In case of GitOps, Flux might complain that the app manifest is invalid as the `spec.version` field is mandatory. In that case, edit the live App CR and set `spec.version` to an empty string. That will unblock Flux and allow it reconcile successfully. And if you want to use `kubectl-gs` to create a cluster, you'd need to now specify the release version, e.g.: ```bash -kubectl-gs template cluster --provider vsphere --organization my_org --name cluster_name -vsphere-network-name network_name --release v27.0.1 +kubectl-gs template cluster --provider vsphere --organization my_org --name cluster_name -vsphere-network-name network_name --release 27.0.1 ```