-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Demonstrate how a TKG cluster can be upgrade using TF 3.12.0 #1237
Comments
Hi @returntrip,
Yes. The OVA names that appear there can be used to upgrade the cluster.
Also yes. The components mentioned in that documentation page (CAPVCD, CSI, CPI versions) are calculated during cluster creation phase with the In other words, these components only need to be updated if you created the cluster with CSE 4.1.X and you recently updated to 4.2.X. So, if you are not upgrading CSE in VCD, but only your cluster, you can use |
Thanks for the quick reply. It would be great to see an example with the end to end process to upgrade a TKG cluster and its K8s components from say C.S.E 4.1.1 to CSE 4.2.0. It would be especially good to see a TF example code template.
…On Tue, 26 Mar 2024, at 11:21, Adam Barreiro wrote:
Hi @returntrip <https://github.com/returntrip>,
> Does it mean that you can upgrade the TKG cluster using "supported_upgrades <https://registry.terraform.io/providers/vmware/vcd/latest/docs/resources/cse_kubernetes_cluster#supported_upgrades>" while keeping the Kubernetes Components to the version currently installed in the TKG cluster?
>
Yes. The OVA names that appear there can be used to upgrade the cluster.
> But if you wan to have lastest K8s components you must first upgrade the components <https://docs.vmware.com/en/VMware-Cloud-Director-Container-Service-Extension/4.1/VMware-Cloud-Director-Container-Service-Extension-Using-Tenant-4.1/GUID-092C40B4-D0BA-4B90-813F-D36929F2F395.html> and then use supported_upgrades?
>
Also yes. The components mentioned in that documentation page (CAPVCD, CSI, CPI versions) are calculated during cluster creation phase with the `cse_version` argument (as these are obtained from CSE configuration). At the moment, `cse_version` cannot be changed (for example, from `4.1.0` to `4.2.0`) as it requires this manual step.
In other words, these components only need to be updated if you created the cluster with CSE 4.1.X and you recently updated to 4.2.X. So, if you are *not upgrading CSE in VCD, but only your cluster*, you can use `supported_upgrades` for that and no other step is required.
—
Reply to this email directly, view it on GitHub <#1237 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADLHVOXBCA5DCK7WWDPESTLY2E42PAVCNFSM6AAAAABFHJU5JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRQGA2DGMBTHE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi @returntrip, thanks for spotting that. It is, indeed and unfortunately, a bug. Thank you very much for the feedback. As per the upgrade from C.S.E 4.1.1 to CSE 4.2.0, I'm working on that. |
Update: What I wanted to do is basically unsupported:). I was trying to go minor version +2 (i.e. 1.26 to 1.28). The relevant thing do is that the erros should say something like: "Unsupported Version. K8s version is too new" hi @adambarreiro I have done some quick testing (using TFV 3.12.1) for this:
|
@adambarreiro
Community Note
Description
Would be nice to have an example of how a TKG cluster upgrade from TKG v 2.2.0 to TKG v.2.4.0 works.
I am reading the current documentation and this bit is particularly confusing:
"Upgrading CSE version with cse_version is not supported as this operation would require human intervention, as stated in the official documentation."
Does it mean that you can upgrade the TKG cluster using "supported_upgrades" while keeping the Kubernetes Components to the version currently installed in the TKG cluster?
But if you wan to have lastest K8s components you must first upgrade the components and then use
supported_upgrades
?Would be great to see how the upgrade works in practice. Thanks
New or Affected Resource(s)
vcd_cse_kubernetes_cluster
Terraform Configuration (if it applies)
NA
References
https://registry.terraform.io/providers/vmware/vcd/latest/docs/resources/cse_kubernetes_cluster#updating
The text was updated successfully, but these errors were encountered: