Skip to content

Meta Issue for k8s 1.34 bump #7020

Description

@acornett21

Meta Issue for k8s 1.34 bump

In order to bump Operator SDK to support Kubernetes 1.34 there are a few dependencies we rely on making the bump first.
This issue is meant to help track all dependencies and the status of their bumps.

Order of dependency bumps

Step 1: upgrade controller-runtime, controller-tools, helm, and operator-framework/operator-manifest-tools(can be done in parallel)

Step 2: upgrade operator-framework/api (can be done immediately after controller-runtime & controller-tools)

Step 3.1: upgrade operator-framework/operator-registry and operator-framework/operator-lib (can be done immediately after operator-framework/api)

Step 3.2: upgrade kubebuilder

Step 4: upgrade operator-framework plugins

  • operator-framework/ansible-operator-plugins

Step 5: upgrade operator-framework/operator-sdk dependencies

  • Bump Ginkgo/v2 and Kubebuilder 1.34
  • Bump SDK to use k8s 1.34

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions