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.

Sign up for GitHub

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

Jump to bottom

Epic - Day 2 Upgrade Process for Cluster Workloads #175

Open
lb4368 opened this issue Jun 15, 2021 · 0 comments
Open

Epic - Day 2 Upgrade Process for Cluster Workloads #175

lb4368 opened this issue Jun 15, 2021 · 0 comments
Labels
design needed Requires design approach/discussion enhancement New feature or request epic This is an epic issue priority/critical Items critical to be implemented, usually by the next release
Milestone
Future

Comments

@lb4368
Copy link

lb4368 commented Jun 15, 2021

Problem description
As an operator, I want a defined plan/process for deploying upgrades to workload resources within my target Kubernetes cluster, so that upgrades are delivered in a consistent manner that will simplify upgrade configuration and reduce upgrade errors.

Proposed change
Design and develop an upgrade process that encapsulates common phases of an upgrade and allows for configuration of the upgrade steps. The process must address:

  • Manifest structures for upgradeable workload resources to support the upgrade path
  • Dependency/pre-requisite checking and validation prior to applying upgrades
  • Applying an upgrade to a target cluster and/or sub-cluster(s)
  • Upgrade validation/error handling/rollback

See https://hackmd.io/0Sw53doBSwiOzgfzYrfmRQ for design discussion
@lb4368 lb4368 added enhancement New feature or request triage design needed Requires design approach/discussion epic This is an epic issue labels Jun 15, 2021
@jezogwza jezogwza removed the triage label Jun 16, 2021
@jezogwza jezogwza added this to the Future milestone Jun 16, 2021
@jezogwza jezogwza added the priority/critical Items critical to be implemented, usually by the next release label Jun 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design needed Requires design approach/discussion enhancement New feature or request epic This is an epic issue priority/critical Items critical to be implemented, usually by the next release
Projects
None yet
Milestone
Future
Development

No branches or pull requests
2 participants
@lb4368 @jezogwza