Red Hat Integration -- Service Registry -- will breaking changes in the PodDisrpuptionBudget API in OCP 4.12 block an OCP upgrade?

Solution Verified - Updated -

Issue

According to the OpenShift release notes for version 4.12, the API PodDisruptionBudget:policy/v1beta1 has been removed, and replaced with v1. Since the Service Registry operator uses this API, there is some uncertainty about whether it's safe to upgrade a cluster to 4.12 when this operator is installed.

Environment

  • Red Hat OpenShift Container Platform
    • 4.12
  • Red Hat Integration - Service Registry
    • 2.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content