move post-kuberentes-push-images job back to test-infra-trusted

[spiffxp]

it relies on secrets not yet available in k8s-infra-prow-build-trusted

[spiffxp]

job will need to be retried after merge https://testgrid.k8s.io/sig-testing-images#post-kubernetes-push-images

[spiffxp]

/test pull-test-infra-bazel
network flakiness

[spiffxp]

/test pull-test-infra-bazel
I'm beginning to wonder if our RBE worker pool is unhealthy

ERROR: An error occurred during the fetch of repository 'bazel-base':
   Pull command failed: 2020/05/06 16:05:41 Running the Image Puller to pull images from a Docker Registry...
2020/05/06 16:05:42 Image pull was unsuccessful: unable to save remote image gcr.io/k8s-testimages/launcher.gcr.io/google/bazel@sha256:cefc822f93bb3dcf272ce3e4c5162b179d5c165584ace13856afed99662b87cd: unable to write image layers: unable to write image layer: unable to write the contents of layer 0 to /bazel-scratch/.cache/bazel/_bazel_root/05618a594cb3499a4b912817865867cd/external/bazel-base/image/000.tar.gz: read tcp 10.60.41.57:60546->108.177.112.128:443: read: connection reset by peer
 (/bazel-scratch/.cache/bazel/_bazel_root/05618a594cb3499a4b912817865867cd/external/go_puller_linux/file/downloaded -directory /bazel-scratch/.cache/bazel/_bazel_root/05618a594cb3499a4b912817865867cd/external/bazel-base/image -os linux -os-version  -os-features  -architecture amd64 -variant  -features  -name gcr.io/k8s-testimages/launcher.gcr.io/google/bazel@sha256:cefc822f93bb3dcf272ce3e4c5162b179d5c165584ace13856afed99662b87cd)

[spiffxp]

/test pull-test-infra-bazel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: michelle192837, spiffxp

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/image-pushing/OWNERS [michelle192837]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@spiffxp: Updated the job-config configmap in namespace default at cluster default using the following files:

• key k8s-staging-e2e-test-images.yaml using file config/jobs/image-pushing/k8s-staging-e2e-test-images.yaml

In response to this:

it relies on secrets not yet available in k8s-infra-prow-build-trusted

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.