Rishi Misra

@gbaned trying to understand if I need to do anything at my end. I presume this PR is in some "queue" waiting to be integrated. Tx.

There are few regressions spotted on `s390x` due to this commit - I am pulling back PR until a solution is found. Thx.

@kaovilai Thanks for following up on this PR. For this iteration, is it possible to release artifacts similar to [this](https://github.com/vmware-tanzu/velero/pull/1605) `ppc64le` implementation? I am unable to determine `ppc64le` CI is...

> > @kaovilai Thanks for following up on this PR. For this iteration, is it possible to release artifacts similar to [this](https://github.com/vmware-tanzu/velero/pull/1605) `ppc64le` implementation? I am unable to determine `ppc64le`...

> See if this would work for you in the meantime. > > ``` > docker container create --name velero-s390x --platform=linux/s390x registry.redhat.io/oadp/oadp-velero-rhel9:1.4.0 && \ > docker cp velero-s390x:/velero ./velero &&...

Thanks @zubron - for now it can be built on `s390x` by simply specifying `RESTIC_VERSION=0.12.1` during `make all-containers` step. Would it make sense to add a blurb in the docs...

@zubron if it makes sense I can PR changes as per #4047. Let me know your thoughts. Thanks.

Hi @zubron - just wanted to follow-up on this issue. I also noticed that in order for testcases (`make test`) to run on `s309x` we will require some changes to...

Thanks @zubron for your comments. Yes, my development platform is `s390x` and my intention was to run through the testcases to make sure `velero` works on this platform. I also...

Hi @zubron - just a quick follow up on adding this platform to the build targets. I think we have pretty much everything in place now. Thanks for your patience...