Epic: Bring Providers to Crossplane V2

Open
#233 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes
Domain
cloud, infrastructure

Research direction

Start with the checked compatibility findings in this issue and the linked backlog issue 186; compare the remaining V1/V2 provider, MR readiness, and upgrade-path questions. Done means documenting consequences, selecting upgrade paths and strategies, and recording follow-up items for the BTP, Cloudfoundry, and community providers.

Written by the indexing model from the issue text.

Description

area/provider has parent kind/epic needs/validation
Understand the Epic

Crossplane has released a new version which affects how our Providers operate. Let's collect steps needed to bring the BTP and Cloudfoundry Crossplane Provider to Crossplane V2.

  • [x] Test compatibility Crossplane V2 with providers V1 -> Does not work, provider becomes unhealthy FailedCreateContainer
  • Test compatibility Crossplane V1 with providers V2 -> Works after re-tries (tested with aws V2) --> Provider becomes healthy
  • Test compatibility Crossplane V1 with providers V2 -> Test if MR (old clsuter-scoped and new namespace-scoped MR) become ready/sncyed
  • How do we handle upgrades of all our community providers
  • Exchange with OpenMCP Team on findings
  • Map out Upgrade Path for upgrading a provider
Acceptance Criteria
  • Know consequences of different upgrading approaches
  • Commit to an upgrading path, with follow up items for BTP and CF providers
  • Commit to an upgrading strategy for community providers
Out of scope
  • [ ] Migrating Crossplane V2 on cluster scope with legacy provider -> responsibility of OpenMCP
  • Migrate every Crossplane provider
References
Dominant language
No language data
Stars
1
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openmcp-project/backlog

All issues in openmcp-project/backlog

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.