Skip to content

[Epic] Combine catalogd and operator-controller into a monorepo #1335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
11 tasks done
OchiengEd opened this issue Oct 3, 2024 · 2 comments
Closed
11 tasks done

[Epic] Combine catalogd and operator-controller into a monorepo #1335

OchiengEd opened this issue Oct 3, 2024 · 2 comments
Assignees
Labels
epic v1.x Issues related to OLMv1 features that come after 1.0 v1.1

Comments

@OchiengEd
Copy link
Contributor

OchiengEd commented Oct 3, 2024

Combine OLM v1 components (catalogd and operator-controller) into a monorepo by importing catalogd apis and packages into the operator-controller.

This will build upon the work done in the RFC

In summary, the task should be completed in two primary phases:

  1. Migration
  2. Merging

Tasks

Phase 1

The following ones might be blocked by a new release with the Monorepo structure, but we should ensure that we have the required artefacts before doing the release.

@OchiengEd OchiengEd changed the title [Epic] Merge catalogd and operator-controller into a monorepo [Epic] Combine catalogd and operator-controller into a monorepo Oct 3, 2024
@LalatenduMohanty LalatenduMohanty added the v1.x Issues related to OLMv1 features that come after 1.0 label Oct 3, 2024
@joelanford joelanford added this to OLM v1 Oct 3, 2024
@grokspawn grokspawn moved this to Implementing in OLM v1 Oct 4, 2024
@jsm84
Copy link
Contributor

jsm84 commented Nov 21, 2024

Linked this to EET-4412 epic in Jira.

@m1kola m1kola added the epic label Nov 26, 2024
@LalatenduMohanty LalatenduMohanty added v1.1 and removed v1.x Issues related to OLMv1 features that come after 1.0 labels Dec 2, 2024
@LalatenduMohanty LalatenduMohanty moved this from Implementing to Accepted in OLM v1 Dec 3, 2024
@LalatenduMohanty LalatenduMohanty added the v1.x Issues related to OLMv1 features that come after 1.0 label Dec 10, 2024
@grokspawn grokspawn moved this from Accepted to Implementing in OLM v1 Jan 13, 2025
@camilamacedo86 camilamacedo86 self-assigned this Jan 29, 2025
@camilamacedo86
Copy link
Contributor

camilamacedo86 commented Jan 29, 2025

PS: This is an experimental release candidate v1.2.0-rc2 , incorporating changes from the monorepo initiative. (More info: Issue #1335). The goal of this release is to properly validate these changes and make any necessary adjustments.

⚠️ This is a pre-release candidate, so if you encounter any issues, please let us know!
🙌 Huge thanks to all our contributors for making this happen! 🚀

@camilamacedo86 camilamacedo86 moved this from Implementing to Done in OLM v1 Jan 29, 2025
@camilamacedo86 camilamacedo86 moved this from Done to Ready for Review in OLM v1 Jan 29, 2025
@camilamacedo86 camilamacedo86 moved this from Ready for Review to Implementing in OLM v1 Jan 29, 2025
@camilamacedo86 camilamacedo86 moved this from Implementing to Ready for Review in OLM v1 Feb 4, 2025
@camilamacedo86 camilamacedo86 moved this from Ready for Review to Implementing in OLM v1 Feb 4, 2025
@camilamacedo86 camilamacedo86 moved this from Implementing to Done in OLM v1 Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic v1.x Issues related to OLMv1 features that come after 1.0 v1.1
Projects
Archived in project
Development

No branches or pull requests

5 participants