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

Kubernetes uplift to v1.21 & Establish general pattern for K8s upgrades #589

Closed
eak13 opened this issue Jun 24, 2021 · 4 comments
Closed
Assignees
Labels
design needed New Design or Redesign required enhancement New feature or request priority/medium Default priority for items
Milestone

Comments

@eak13
Copy link

eak13 commented Jun 24, 2021

Problem description
Kubernetes has a cadence of posting a new release every 3 to 6 months. A release has roughly a 12 - 14 month lifespan. To maintain CNCF certification, conformance (like Anuket) & currency with the latest releases, Airship needs to establish an ongoing cadence to continually uplift the supported Kubernetes version.

v1.21 was released for GA on 5/12/2021. While there are current efforts underway to uplift to v1.20 (#555, #556, #569, #570, #571), we want to shift to v1.21 for Airship v2.1. Ideally, with the v1.21 uplift, we establish a more general pattern of Kubernetes upgrades where we are not necessarily focusing on the individual providers.

K8s release information can be found here: https://kubernetes.io/releases/

Tasks

  • Determine more general approach for k8s upgrade (design call topic - see notes).
  • Ensure image builder images reflect v1.21
  • Using this approach, uplift the k8s version to v1.21 for:
    • Bare Metal - First priority
    • Azure - First priority
    • Docker - First priority
    • GCP - Second priority
    • Openstack - Second priority
@eak13 eak13 added enhancement New feature or request triage Needs evaluation by project members epic Features or large improvements reflected as a list of issues design needed New Design or Redesign required and removed epic Features or large improvements reflected as a list of issues labels Jun 24, 2021
@eak13 eak13 added this to the v2.2 milestone Jun 24, 2021
@eak13 eak13 modified the milestones: v2.2, Future Jun 24, 2021
@jezogwza jezogwza modified the milestones: Future, v2.1 Jul 7, 2021
@eak13 eak13 changed the title Establish Airshipctl upgrade cadence to maintain currency with Kubernetes upgrades Kubernetes uplift to v1.21 & Establish general pattern for K8s upgrades Jul 9, 2021
@jezogwza jezogwza added priority/medium Default priority for items and removed triage Needs evaluation by project members labels Jul 14, 2021
@eak13
Copy link
Author

eak13 commented Jul 15, 2021

Discussion of approach from 7/15 design call:

Providers:

  • Work backwards to the providers to ensure compatibility
  • Determine if we need to upgrade the CAPI provider to support the K8s upgrade? Hopefully decoupled events, but may be some dependencies
  • Use catalog overrides if issues with v1.21 or not supported

@diwrajchitoor
Copy link
Contributor

Can someone assign this to me

@rkjain
Copy link
Contributor

rkjain commented Sep 16, 2021

Hi, The patch set to uplift docker version to 1.21 is here - https://review.opendev.org/c/airship/airshipctl/+/795582
@eak13 - Can you also create a separate issue for uplifting docker version and assign it to me.

airshipbot pushed a commit to airshipit/images that referenced this issue Sep 24, 2021
airshipit/airshipctl#589

Change-Id: I2141b4637ffa9ebbd22ba6c46421a97e901dda12
Signed-off-by: diwakar thyagaraj <dt241s@att.com>
airshipbot pushed a commit that referenced this issue Nov 1, 2021
This upgrades Kubernetes version in airshipctl to v1.21.2

Depends on https://review.opendev.org/c/airship/image-builder/+/812013/

https: //github.com//issues/589
Change-Id: I30ef2543d91f574e73a555bf67ab7ec2764a4411
Signed-off-by: diwakar thyagaraj <dt241s@att.com>
@eak13
Copy link
Author

eak13 commented Nov 3, 2021

@eak13 eak13 closed this as completed Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design needed New Design or Redesign required enhancement New feature or request priority/medium Default priority for items
Projects
None yet
Development

No branches or pull requests

4 participants