Skip to content

already handled nodes should be skipped when kubeone retries the upgrade of static workers #4059

Description

@soer3n

Description of the feature you would like to add / User story

When kubeone tries to upgrade static workers and one fails, it always starts from the beginning and is not skipping already upgraded nodes.

As a kubeone user
I would like to skip already upgraded nodes when kubeone retries the upgrade process after a static worker upgrade failed.

Solution details

  • when kubeone retries the upgrade of static workers after it failed on one node it should check if a static worker was already upgraded and skip the upgrade loop for that worker.

Alternative approaches

Use cases

Additional information

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.sig/cluster-managementDenotes a PR or issue as being assigned to SIG Cluster Management.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions