Loading...

XML

Word

Printable

Type: Initiative
Resolution: Unresolved
Priority: Major
Fix Version/s: None
Affects Version/s: rhos-19.0.0
Component/s: OpenStack on OpenShift Core
Labels:
None

Severity:
Critical
Color Status:
Not Selected
Ready:
False
Blocked:
False
Blocked Reason:

Hide

None

Show
None

Cost of Delay:
0
PM Score:
0
Hierarchy Progress Bar:

100% To Do, 0% In Progress, 0% Done

AssignedTeam:
rhos-conplat-core-operators

Initiative Overview

CRDs in our operators are versioned. As a convention almost all of our APIs have an initial version of 'v1beta1'. This initiative is meant to support the general semantics needed to support an upgrade path from a 'v1beta1' to a new API version for example called 'v1beta2'.

Goals

Support CRD updates.

Done - Acceptance Criteria

Support all of the needs outlined in the upstream dev-doc PR: https://github.com/openstack-k8s-operators/dev-docs/pull/146

is depended on by

RHOSSTRAT-924 Create the next non backward compatible CRD version

relates to

OSPRH-19147 service account need to have ownership updated during a CRD update

Backlog

OSPRH-18527 Collect the generic non backward compatible CRD changes we want to schedule for v2 CRD

Backlog

OSPRH-15649 demonstrate how we would handle a new CRD version (conversion webhooks, etc)

Closed

Assignee:: Dan Prince

Reporter:: Dan Prince

Team:: rhos-conplat-core-operators

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2025/08/15 6:58 PM

Updated:: 2025/12/01 8:18 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates

PagerDuty