Skip to content

upgrade: Make node components upgradeable (at all possible) #3333

@davidopp

Description

@davidopp

@brendandburns (couldn't find alex m. or eric h. on github?) please correct/elaborate any details here...

There are different ways to skin this cat but I think the approach we decided on was:

  • cron job on node looks for new version of {kubelet, proxy, ...} and when it finds one, kills currently running version (send a signal for clean shutdown first?) and starts new version [this can be made arbitrarily more complicated, like falling back to old version if new version doesn't work, but better to keep it simple for now]
  • out-of-band mechanism to push new version of these components to the nodes (we didn't really talk about this -- how does this work? Salt?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority/backlogHigher priority than priority/awaiting-more-evidence.sig/cluster-lifecycleCategorizes an issue or PR as relevant to SIG Cluster Lifecycle.sig/nodeCategorizes an issue or PR as relevant to SIG Node.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions