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

Spike: CAPI Component Upgrades for Brownfield Sites #609

Closed
lb4368 opened this issue Jul 12, 2021 · 3 comments
Closed

Spike: CAPI Component Upgrades for Brownfield Sites #609

lb4368 opened this issue Jul 12, 2021 · 3 comments
Assignees
@SirishaGopigiri
Labels
Day2 Relates to day 2 operations (brownfield upgrades, etc.) enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release size l
Milestone
v2.1

Comments

@lb4368
Copy link

lb4368 commented Jul 12, 2021 •
edited
Loading

Problem description
Would like to understand the implications of an update to existing CAPI components (Cluster API, Bootstrap Provider, and Control Plane Provider) in a site (brownfield scenario).

https://cluster-api.sigs.k8s.io/tasks/upgrading-cluster-api-versions.html

Proposed change
Investigate and document a plan for an upgrade of CAPI components (currently to latest v1alpha4 version) on an existing cluster.

  • Identify dependencies and constraints such as K8s versions, infrastructure provider versions, etc.
  • Investigate integration of clusterctl upgrade into airshipctl
  • Identify impacts to cluster availability and performance during an upgrade
@lb4368 lb4368 added enhancement New feature or request triage Needs evaluation by project members labels Jul 12, 2021
@lb4368 lb4368 added this to the v2.2 milestone Jul 12, 2021
@lb4368 lb4368 added the Day2 Relates to day 2 operations (brownfield upgrades, etc.) label Jul 12, 2021
@lb4368 lb4368 mentioned this issue Jul 12, 2021
Closed
@SirishaGopigiri
Copy link
Contributor

Please assign it to me, as I am working on upgrade #518 so I will look at this as well.

@jezogwza jezogwza added priority/critical Items critical to be implemented, usually by the next release and removed triage Needs evaluation by project members labels Jul 14, 2021
@eak13 eak13 added the size l label Jul 26, 2021
@SirishaGopigiri
Copy link
Contributor

Related hackmd.io https://hackmd.io/8OXbEcpQTY-P-aoRqFG_WA

@eak13
Copy link

eak13 commented Sep 15, 2021

Closing per above

@eak13 eak13 closed this as completed Sep 15, 2021
@eak13 eak13 modified the milestones: v2.2, v2.1 Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SirishaGopigiri SirishaGopigiri

Labels
Day2 Relates to day 2 operations (brownfield upgrades, etc.) enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release size l
Projects
None yet
Milestone
v2.1
Development

No branches or pull requests
4 participants
@lb4368 @eak13 @jezogwza @SirishaGopigiri