Skip to content

Conversation

@m1kola
Copy link
Contributor

@m1kola m1kola commented May 7, 2025

Summary

Instead of relying on MEKO -> MCK upgrade path in a catalog metadata, we now use uninstall-then-install migration approach.

While MEKO -> MCK upgrade path is technically possible, it is not allowed in operatorhub.io and Red Hat certified operators catalogs as it is prevented by validation.

Proof of Work

CI must be green.

Checklist

  • Have you linked a jira ticket and/or is the ticket in the title?
  • Have you checked whether your jira ticket required DOCSP changes?
  • Have you checked for release_note changes?

Reminder (Please remove this when merging)

  • Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
  • Our Short Guide for PRs: Link
  • Remember the following Communication Standards - use comment prefixes for clarity:
    • blocking: Must be addressed before approval.
    • follow-up: Can be addressed in a later PR or ticket.
    • q: Clarifying question.
    • nit: Non-blocking suggestions.
    • note: Side-note, non-actionable. Example: Praise
    • --> no prefix is considered a question
Instead of relying on MEKO -> MCK upgrade path in a catalog, we use uninstall-then-install migration approach. While MEKO -> MCK upgrade path is technically possible, it is not allowed by validation in Red Hat certified catalogs.
@m1kola m1kola marked this pull request as ready for review May 7, 2025 20:57
@m1kola m1kola requested a review from a team as a code owner May 7, 2025 20:57
This is to simulate rescheduling and ensure that the workloads are still working after MEKO uninstallation.
@m1kola m1kola merged commit 78beae6 into mongodb:master May 9, 2025
35 checks passed
@m1kola m1kola deleted the update_meko_to_mck_olm_tests branch May 9, 2025 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants