Skip to content
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

Zero downtime upgrade #59

Open
alubbock opened this issue Mar 14, 2023 · 1 comment
Open

Zero downtime upgrade #59

alubbock opened this issue Mar 14, 2023 · 1 comment

Comments

@alubbock
Copy link

Would it be possible to enact Talos upgrades just by specifying a new image ID? By default, it seems that all VMs would be destroyed and recreated, which would probably break the cluster.

Terraform gives an example of zero downtime upgrades that utilises create_before_destroy = true combined with a local-exec to run a healthcheck before the original is destroyed:

resource "digitalocean_droplet" "web" {
  count  = 2
  image  = "${var.image}"
#...
  lifecycle {
    create_before_destroy = true
  }

  provisioner "local-exec" {
    command = "./check_health.sh ${self.ipv4_address}"
  }

Would it be possible to use local-exec to execute talosctl health? It would probably fail during initial cluster bootstrapping, so it'd need to workaround that to only run on upgrades.

@smira
Copy link
Member

smira commented Mar 6, 2024

This provider doesn't support talosctl upgrade at the moment, and VM being re-created on image change is not related to this provider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants