From ebdf80d93719f4208bf1543454aa68c0be417188 Mon Sep 17 00:00:00 2001 From: Mark Rossetti Date: Wed, 16 Feb 2022 13:25:33 -0800 Subject: [PATCH] Adding prow job to push windows-gmsa-webhook image Signed-off-by: Mark Rossetti --- .../k8s-staging-gmsa-webhook.yaml | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 config/jobs/image-pushing/k8s-staging-gmsa-webhook.yaml diff --git a/config/jobs/image-pushing/k8s-staging-gmsa-webhook.yaml b/config/jobs/image-pushing/k8s-staging-gmsa-webhook.yaml new file mode 100644 index 0000000000000..29e062f2704d6 --- /dev/null +++ b/config/jobs/image-pushing/k8s-staging-gmsa-webhook.yaml @@ -0,0 +1,28 @@ +postsubmits: + kubernetes-sigs/windows-gmsa: + # The name should be changed to match the repo name above + - name: post-gmsa-webhook-push-images + cluster: k8s-infra-prow-build-trusted + annotations: + testgrid-dashboards: sig-windows-push-images, sig-k8s-infra-gcb + testgrid-tab-name: post-gmsa-webhook-push-images + decorate: true + # this causes the job to only run on the master branch. Remove it if your + # job makes sense on every branch (unless it's setting a `latest` tag it + # probably does). + branches: + - ^master$ + spec: + serviceAccountName: gcb-builder + containers: + - image: gcr.io/k8s-staging-test-infra/image-builder:v20211014-7ca1952a94 + command: + - /run.sh + args: + # this is the project GCB will run in, which is the same as the GCR + # images are pushed to. + - --project=k8s-staging-gmsa-webhook + # This is the same as above, but with -gcb appended. + - --scratch-bucket=gs://k8s-staging-gmsa-webhook-gcb + - --env-passthrough=PULL_BASE_REF + - . \ No newline at end of file