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

Move logic from orchestrate to upgrade script #2928

Commits on Nov 17, 2020

  1. salt: Use cluster_version in upgrade apiserver orchestrate

    Instead of relying on a pillar key `orchestrate.dest_version` in
    orchestrate.apiserver salt states use the `metalk8s.cluster_version` key
    from the pillar (which is the version in the kube-system namespace
    TeddyAndrieux committed Nov 17, 2020
    Configuration menu
    Copy the full SHA
    3c8bab9 View commit details
    Browse the repository at this point in the history
  2. salt,script: Move upgrade logic from orchestrate to script

    Since we use a script and we rely on salt-master running in a static pod
    on the bootstrap node we need to move some logic outside of the salt
    orchestrate to the script so that salt-master restart can be handled
    properly (and not brutaly interupt a salt orchestrate execution.
    - Etcd cluster upgrade is now part of the upgrade script
    - All APIServers upgrade is now part of the uppgrade script
    - Upgrade bootstrap engines (kubelet + containerd) locally
    - Then call the orchestrate to upgrade all nodes one by one
    This commit also add a warning in the upgrade orchestrate so that we now
    that this orchestrate is only a part of the upgrade process
    
    Fixes: #2908
    TeddyAndrieux committed Nov 17, 2020
    Configuration menu
    Copy the full SHA
    9f9c2eb View commit details
    Browse the repository at this point in the history
  3. salt: Upgrade orchestrate small improvement

    Do no longer provide `orchestrate.dest_version` pillar key to
    `upgrade.precheck` as it do not use it, update `require_in` so that we
    no longer run `Deploy Kubernetes service config objects` if one node
    upgrade failed
    TeddyAndrieux committed Nov 17, 2020
    Configuration menu
    Copy the full SHA
    fa5c8e1 View commit details
    Browse the repository at this point in the history