Bug: The OADP should have an organization in quay w/ multiple owners where sample-app containers can be pushed and used in CI

[weshayutin]

Contact Details

whayutin@redhat.com

Describe bug

The sample-apps we're using in tests/e2e will start to support multi-arch builds which require multi-arch manifests and pushed as a single container manifest into quay. FYI.. it appears to that one container is present, however multiple arches are supported.

The source code for the sample-apps and the manifests should be present in https://github.com/konveyor/mig-demo-apps

Ideally we also create ci directly on the mig-demo-apps repo so we can be sure things will work properly w/o OADP or other projects failing.

What happened?

We're going multi-arch baby

OADP Version

1.0.1 (Stable)

OpenShift Version

4.10

Velero pod logs

No response

Restic pod logs

No response

Operator pod logs

No response

New issue

• This issue is new

[kaovilai]

If we do source to image, we won't need this.
Alternative to quay we can also use github container registry ghcr.io which publishes packages to https://github.com/orgs/konveyor/packages

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Mathieu-Ferraton]

@weshayutin @kaovilai We are now using this quay.io/migqe repo to store multi-arch images used in the downstream CI. Maybe we can push upstream CI app images there as well. What do you think?

[kaovilai]

Sounds good to me.

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.