Skip to content

Update MEKO to MCK OLM tests #97

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
May 9, 2025
Merged

Update MEKO to MCK OLM tests #97

merged 2 commits into from
May 9, 2025

Conversation

m1kola
Copy link
Contributor

@m1kola m1kola commented May 7, 2025 •
edited
Loading

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

@m1kola m1kola force-pushed the update_meko_to_mck_olm_tests branch from 2506ad9 to ff24026 Compare May 7, 2025 18:24
@m1kola
Update OLM tests to different migration option
8f5c02e 
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 force-pushed the update_meko_to_mck_olm_tests branch from ff24026 to 8f5c02e Compare May 7, 2025 18:34
@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
nammn
nammn approved these changes May 8, 2025
View reviewed changes
@m1kola
Kill STS pods after MEKO uninstall
1e49e9f 
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
Reviewers

@nammn nammn nammn approved these changes

@anandsyncs anandsyncs anandsyncs approved these changes

@Julien-Ben Julien-Ben Julien-Ben approved these changes

@fealebenpae fealebenpae Awaiting requested review from fealebenpae fealebenpae is a code owner automatically assigned from mongodb/kubernetes-hosted

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@m1kola @anandsyncs @nammn @Julien-Ben