-
Notifications
You must be signed in to change notification settings - Fork 18
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
gracefull upgrades through terraform #140
Comments
IMHO, this is by far one of the most important functionalities missing in the Talos Terraform provider. To manage a Talos K8s cluster using only Terraform, we need a declarative and idempotent way to specify a target version. The lifecycle of a cluster should be considered more thoroughly. The Talos and Kubernetes versions also have be compatible with the additional components that may be needed, such as external CCM, CNI, CSI, etc. Talos introduces imperative change management here, which is undesirable in a Terraform environment. Therefore, I don't see any feasible way to conduct proper lifecycle management with this module. |
As a workaround you can specify the Not pretty but bast we can do right now besides from gracefully replacing nodes |
Yeah, without a way to run |
This could be done with different "vm instance/server/etc" blocks, the initial block would create and destroy on any update and the second block would depend on data http to connect before creating/destroying. This is only for upgrading Talos and not k8s. |
Currently there is no option to trigger talos upgrade through terraform provider.
If I aplly new kubernetes version through talos resources all nodes get patched simultaneously.
It would be great to have resources to upgrade both talos itself and kubernetes in a gracefull way one by one node (like
talosctl upgrade
andtaloscyl upgrade-k8s
does).Another option could be, to have builtin upgrade controller in talos controllers.
The text was updated successfully, but these errors were encountered: