From fd684f5c051bc72c108e2ee0e368b9e9d849fda6 Mon Sep 17 00:00:00 2001 From: t-qini Date: Tue, 10 Dec 2019 13:53:48 +0800 Subject: [PATCH] Add prow job config for pushing cloud provider azure image to gcr staging repo. --- .../k8s-staging-provider-azure.yaml | 40 +++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 config/jobs/image-pushing/k8s-staging-provider-azure.yaml diff --git a/config/jobs/image-pushing/k8s-staging-provider-azure.yaml b/config/jobs/image-pushing/k8s-staging-provider-azure.yaml new file mode 100644 index 0000000000000..cff6db52e6fe6 --- /dev/null +++ b/config/jobs/image-pushing/k8s-staging-provider-azure.yaml @@ -0,0 +1,40 @@ +postsubmits: + # This is the github repo we'll build from. This block needs to be repeated + # for each repo. + kubernetes-sigs/some-repo-name: + # The name should be changed to match the repo name above + - name: post-provider-azure-push-images + cluster: test-infra-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-provider-azure-image-pushes + 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: + 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-provider-azure + # This is the same as above, but with -gcb appended. + - --scratch-bucket=gs://k8s-staging-cluster-api-gcb + - --env-passthrough=PULL_BASE_REF + - . + env: + - name: GOOGLE_APPLICATION_CREDENTIALS + value: /creds/service-account.json + volumeMounts: + - name: creds + mountPath: /creds + volumes: + - name: creds + secret: + secretName: deployer-service-account