[dnm] workflows/test: use 'dev-latest' s3gw image

[jecluis]

This patch set attempts to have tests running out of a dev-latest version of the s3gw container in quay¹.

Footnotes

1. which currently doesn't exist, nor gets built. Should this work, however, that would be the next step. ↩

[jecluis]

Okay, cool. It failed with

Type     Reason            Age                   From               Message
  ----     ------            ----                  ----               -------
  Warning  FailedScheduling  8m6s (x2 over 8m20s)  default-scheduler  0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
  Normal   Scheduled         8m4s                  default-scheduler  Successfully assigned s3gw-atboa0f5l1/s3gw-atboa0f5l1-s3gw-99c5f48ff-2h4wb to chart-testing-control-plane
  Normal   Pulling           6m36s (x4 over 8m3s)  kubelet            Pulling image "quay.io/s3gw/s3gw:dev-latest"
  Warning  Failed            6m36s (x4 over 8m3s)  kubelet            Failed to pull image "quay.io/s3gw/s3gw:dev-latest": rpc error: code = NotFound desc = failed to pull and unpack image "quay.io/s3gw/s3gw:dev-latest": failed to resolve reference "quay.io/s3gw/s3gw:dev-latest": quay.io/s3gw/s3gw:dev-latest: not found
  Warning  Failed            6m36s (x4 over 8m3s)  kubelet            Error: ErrImagePull
  Warning  Failed            6m25s (x6 over 8m3s)  kubelet            Error: ImagePullBackOff
  Normal   BackOff           3m3s (x20 over 8m3s)  kubelet            Back-off pulling image "quay.io/s3gw/s3gw:dev-latest"

Which means this is the way to force it to get a potential dev image. Now to figure out how to do that on the s3gw repository.

[jecluis]

This could potentially rely on the nightly builds instead.