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

Upgrade of 2A #308

Open
DinaBelova opened this issue Sep 16, 2024 · 0 comments
Open

Upgrade of 2A #308

DinaBelova opened this issue Sep 16, 2024 · 0 comments
Assignees
Labels
epic Large body of work, can be broken down into individual issues

Comments

@DinaBelova
Copy link
Collaborator

DinaBelova commented Sep 16, 2024

Goals

Major deliverables

  • A simple 2A upgrade system which follows k8s best practices and allows a platform lead to update the 2A systems and manage any dependencies
  • Automated backup of the 2A and related configuration objects

Who it benefits

  • Customer Business: Stable management solution that continuously receive upgrades that ensure uptime and security
  • Platform Engineering Teams: Stress free upgrades without a massive amount of work to upgrade

Acceptance criteria

  • 2A can be upgraded through a simple update command, that will ensure all the components are upgrade
  • Validation of dependencies and update of related components
    • check if any of the Templates have a dependency on a Major Version of a 2A/CAPx component
  • The ability to gracefully handle the failure to update a component
    • Provide meaningful information on the failure cause
    • Ability for Platform Lead to fix the fault manually (assumption its something easy fixable like a mgmt custer compute node ran out of memory) and tell 2A to continue the update (no automated rollback)
    • Platform Engineer has the possibility to rollback 2A and objects (see AC above) in a manual process
    • No outage impact the running Managed Cluster

Assumptions / out of scope

  • Backup / restore capabilities will be handled as a part of separate discussion / epic. Link - tbd.

Telemetry & Success Criteria

  • Cluster update attempts and status are sent to telemetry with the time and date - The goal is to understand cluster update status
@DinaBelova DinaBelova added the epic Large body of work, can be broken down into individual issues label Sep 16, 2024
@DinaBelova DinaBelova changed the title [placeholder] Upgrade of 2A Upgrade of 2A Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Large body of work, can be broken down into individual issues
Projects
Status: In Progress
Development

No branches or pull requests

2 participants