From edcb5f099e66a7f099822a9c9e668b1767ce0fca Mon Sep 17 00:00:00 2001 From: Manuel Alejandro de Brito Fontes Date: Wed, 20 May 2020 08:51:55 -0400 Subject: [PATCH] Add ingress-nginx push image postsubmit job --- .../k8s-staging-ingress-nginx.yaml | 31 +++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 config/jobs/image-pushing/k8s-staging-ingress-nginx.yaml diff --git a/config/jobs/image-pushing/k8s-staging-ingress-nginx.yaml b/config/jobs/image-pushing/k8s-staging-ingress-nginx.yaml new file mode 100644 index 000000000000..2093316fb24b --- /dev/null +++ b/config/jobs/image-pushing/k8s-staging-ingress-nginx.yaml @@ -0,0 +1,31 @@ +postsubmits: + # This is the github repo we'll build from. This block needs to be repeated + # for each repo. + kubernetes/ingress-nginx: + # The name should be changed to match the repo name above + - name: post-ingress-nginx-push-images + cluster: k8s-infra-prow-build-trusted + annotations: + # This is the name of some testgrid dashboard to report to. + # If this is the first one for your sig, you may need to create one + testgrid-dashboards: sig-network-ingress-nginx + 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-testimages/image-builder:v20190906-d5d7ce3 + 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-ingress-nginx + # This is the same as above, but with -gcb appended. + - --scratch-bucket=gs://k8s-staging-ingress-nginx-gcb + - --env-passthrough=PULL_BASE_REF + - .