Skip to content

Epic: Service Provider CRD Lifecycle Management #690

Description

@christophrj

Understand the Epic

Verify how Service Providers control the lifecycle of CRDs and implement dedicated upgrade checks and CRD lifecycle management.

An upgrade check could be anything as simple as maintaining a list of breaking version changes based on manual assessment to more sophisticated algorithms.

TODO: Align approach and update this description.

Context / Background

Service Provider need to ensure that user requested version changes of a managed domain service do not result in irrepairable deployments caused by API changes between the currently deployed and newly requested domain service version.

User Stories or tasks

No response

What is required to accept the Epic as finished.

  • Service Providers implement version upgrade checks
  • Service Providers block version upgrade if the corresponding upgrade check fails
  • Service Provider CRD lifecycle management is added to the list of Service Provider Quality Criteria
  • Existing Service Providers maintained by SIG extensibility have been updated accordingly

Dependencies of this Epic

No response

Risks of this Epic

No response

Known Stakeholders of this Epic

No response

Milestone Definitions for this Epic.

No response

Metrics Definition for this Epic.

No response

Any further valuable resources.

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

    kind/epicEpic covers multiple issues/tasksneeds/validationVerify Issue and Prio with POsig/extensibilityAll topics related to special interests group openMCP extensibility

    Type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions