Skip to content

Conversation

@perdasilva
Copy link
Collaborator

@perdasilva perdasilva commented Jun 19, 2024

Description of the change:

  • updates our fixture catalogs to decl config
  • updates the kind provisioning process to stand-up with a local registry
  • adds script to build fixture catalogs (against a fixed/versioned opm image - taking it from )
  • adds/refactors command line parameters of the e2e binary to allow the cluster-registry domain to be configurable
  • updates relevant e2e specs to the updated references
  • updates gha e2e to

NOTE: we'll need to update the downstream to push the internal ocp registry and make sure the e2e binary is configured to use it.

Motivation for the change:
Catalog Source images cannot be kind loaded because the Pod is set to Always pull
We wanted to avoid using, e.g. quay. Though, the bundle images are still stored there. And there are still some specific catalog images being used that have been built long ago and live permanently on quay. If we want to target that, that will be a longer story.

Architectural changes:
Before: we stood up a stock kind cluster
Now: We stand-up a local registry side-by-side with kind (largely following their documentation: https://kind.sigs.k8s.io/docs/user/local-registry/).

Related to #3315

Testing remarks:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Bug fixes are accompanied by regression test(s)
  • e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
  • tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
  • Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky and have an issue
  • Code is properly formatted

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 19, 2024
@openshift-ci openshift-ci bot requested review from benluddy and gallettilance June 19, 2024 18:10
@perdasilva perdasilva force-pushed the cleanup/registry branch 7 times, most recently from 17da4ed to fbc4418 Compare June 20, 2024 10:17
@perdasilva perdasilva changed the title [WIP] Cleanup/registry cleanup/registry Jun 20, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 20, 2024
@perdasilva perdasilva changed the title cleanup/registry 🌱 cleanup/registry Jun 20, 2024
@perdasilva perdasilva force-pushed the cleanup/registry branch 7 times, most recently from 45be2e7 to 7df68ff Compare June 26, 2024 15:40
Per Goncalves da Silva added 2 commits June 27, 2024 08:08
@perdasilva perdasilva changed the title 🌱 cleanup/registry [HOLD] 🌱 cleanup/registry Jun 27, 2024
@perdasilva
Copy link
Collaborator Author

Let's hold off on merging until we have the downstream sorted - or at least until Monday

Per Goncalves da Silva added 2 commits July 1, 2024 16:26
Signed-off-by: Per Goncalves da Silva <[email protected]>
Signed-off-by: Per Goncalves da Silva <[email protected]>
@github-actions
Copy link

PRs go stale after 90 days of inactivity. If there is no further activity, the PR will be closed in another 30 days.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 29, 2025
@github-actions
Copy link

This pull request has been closed due to inactivity.

@github-actions github-actions bot closed this Jun 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants