Multiarch support about community-operators

[J0zi]

@ionutz89 @sxd good news! Priorities have changed and we are going to deliver multiarch k8s index.

[dmesser]

@sxd The next big milestone for OperatorHub.io and the operator community is to get ready to adopt the new file-based catalog approach discussed in https://github.com/operator-framework/enhancements/blob/master/enhancements/declarative-index-config.md

However I think having multi-arch catalog is very desireable, so we might be able to get at least the change discussed in this issue done. However producing multi-arch catalogs is probably not solely achieved by this change. Additional logic is needed, the base builder image is just one of the requirements.

[sxd]

@J0zi @mvalarh is it possible that you folks can take a look into this?

[sxd]

@dmesser We know that probably is not the solely change but we need to start at some point and start doing some PRs from there, and basically we need to start by knowing where the image is built and start to do some work on it, otherwise we cannot help, and as you can see there's already people knowing about this and deprecate the use of the old image is important since it can be discarded in the near future.

[sxd]

So for your information the ticket on operator-framework/operator-registry operator-framework/operator-registry#805 has been closed expecting to the community-operator switch images

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[ionutz89]

Any update about it?

[mvalarh]

@sxd we are producing multiarch index image now. Can you please check if ok with you? If ok please close issue. Thanks

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 30 days since being marked as stale.