k8s.io/test-infra@v0.0.0-20240520184403-27c6b4c223d8/config/jobs/image-pushing/k8s-staging-sig-storage.yaml (about) 1 # Automatically generated by k8s-staging-sig-storage-gen.sh. 2 3 postsubmits: 4 kubernetes-csi/csi-driver-host-path: 5 - name: post-csi-driver-host-path-push-images 6 rerun_auth_config: 7 github_team_slugs: 8 - org: kubernetes 9 slug: release-managers 10 - org: kubernetes 11 slug: test-infra-admins 12 - org: kubernetes 13 slug: sig-storage-image-build-admins 14 cluster: k8s-infra-prow-build-trusted 15 annotations: 16 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 17 decorate: true 18 decoration_config: 19 timeout: 240m 20 grace_period: 15m 21 branches: 22 # For publishing canary images. 23 - ^master$ 24 - ^release- 25 # For publishing tagged images. Those will only get built once, i.e. 26 # existing images are not getting overwritten. A new tag must be set to 27 # trigger another image build. Images are only built for tags that follow 28 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 29 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 30 spec: 31 serviceAccountName: gcb-builder 32 containers: 33 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 34 command: 35 - /run.sh 36 args: 37 # this is the project GCB will run in, which is the same as the GCR 38 # images are pushed to. 39 - --project=k8s-staging-sig-storage 40 # This is the same as above, but with -gcb appended. 41 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 42 - --env-passthrough=PULL_BASE_REF 43 - . 44 kubernetes-csi/csi-driver-smb: 45 - name: post-csi-driver-smb-push-images 46 rerun_auth_config: 47 github_team_slugs: 48 - org: kubernetes 49 slug: release-managers 50 - org: kubernetes 51 slug: test-infra-admins 52 - org: kubernetes 53 slug: sig-storage-image-build-admins 54 cluster: k8s-infra-prow-build-trusted 55 annotations: 56 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 57 decorate: true 58 decoration_config: 59 timeout: 240m 60 grace_period: 15m 61 branches: 62 # For publishing canary images. 63 - ^master$ 64 - ^release- 65 # For publishing tagged images. Those will only get built once, i.e. 66 # existing images are not getting overwritten. A new tag must be set to 67 # trigger another image build. Images are only built for tags that follow 68 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 69 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 70 spec: 71 serviceAccountName: gcb-builder 72 containers: 73 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 74 command: 75 - /run.sh 76 args: 77 # this is the project GCB will run in, which is the same as the GCR 78 # images are pushed to. 79 - --project=k8s-staging-sig-storage 80 # This is the same as above, but with -gcb appended. 81 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 82 - --env-passthrough=PULL_BASE_REF 83 - . 84 kubernetes-csi/csi-test: 85 - name: post-csi-test-push-images 86 rerun_auth_config: 87 github_team_slugs: 88 - org: kubernetes 89 slug: release-managers 90 - org: kubernetes 91 slug: test-infra-admins 92 - org: kubernetes 93 slug: sig-storage-image-build-admins 94 cluster: k8s-infra-prow-build-trusted 95 annotations: 96 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 97 decorate: true 98 decoration_config: 99 timeout: 240m 100 grace_period: 15m 101 branches: 102 # For publishing canary images. 103 - ^master$ 104 - ^release- 105 # For publishing tagged images. Those will only get built once, i.e. 106 # existing images are not getting overwritten. A new tag must be set to 107 # trigger another image build. Images are only built for tags that follow 108 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 109 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 110 spec: 111 serviceAccountName: gcb-builder 112 containers: 113 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 114 command: 115 - /run.sh 116 args: 117 # this is the project GCB will run in, which is the same as the GCR 118 # images are pushed to. 119 - --project=k8s-staging-sig-storage 120 # This is the same as above, but with -gcb appended. 121 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 122 - --env-passthrough=PULL_BASE_REF 123 - . 124 kubernetes-csi/external-attacher: 125 - name: post-external-attacher-push-images 126 rerun_auth_config: 127 github_team_slugs: 128 - org: kubernetes 129 slug: release-managers 130 - org: kubernetes 131 slug: test-infra-admins 132 - org: kubernetes 133 slug: sig-storage-image-build-admins 134 cluster: k8s-infra-prow-build-trusted 135 annotations: 136 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 137 decorate: true 138 decoration_config: 139 timeout: 240m 140 grace_period: 15m 141 branches: 142 # For publishing canary images. 143 - ^master$ 144 - ^release- 145 # For publishing tagged images. Those will only get built once, i.e. 146 # existing images are not getting overwritten. A new tag must be set to 147 # trigger another image build. Images are only built for tags that follow 148 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 149 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 150 spec: 151 serviceAccountName: gcb-builder 152 containers: 153 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 154 command: 155 - /run.sh 156 args: 157 # this is the project GCB will run in, which is the same as the GCR 158 # images are pushed to. 159 - --project=k8s-staging-sig-storage 160 # This is the same as above, but with -gcb appended. 161 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 162 - --env-passthrough=PULL_BASE_REF 163 - . 164 kubernetes-csi/external-health-monitor: 165 - name: post-external-health-monitor-push-images 166 rerun_auth_config: 167 github_team_slugs: 168 - org: kubernetes 169 slug: release-managers 170 - org: kubernetes 171 slug: test-infra-admins 172 - org: kubernetes 173 slug: sig-storage-image-build-admins 174 cluster: k8s-infra-prow-build-trusted 175 annotations: 176 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 177 decorate: true 178 decoration_config: 179 timeout: 240m 180 grace_period: 15m 181 branches: 182 # For publishing canary images. 183 - ^master$ 184 - ^release- 185 # For publishing tagged images. Those will only get built once, i.e. 186 # existing images are not getting overwritten. A new tag must be set to 187 # trigger another image build. Images are only built for tags that follow 188 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 189 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 190 spec: 191 serviceAccountName: gcb-builder 192 containers: 193 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 194 command: 195 - /run.sh 196 args: 197 # this is the project GCB will run in, which is the same as the GCR 198 # images are pushed to. 199 - --project=k8s-staging-sig-storage 200 # This is the same as above, but with -gcb appended. 201 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 202 - --env-passthrough=PULL_BASE_REF 203 - . 204 kubernetes-csi/external-provisioner: 205 - name: post-external-provisioner-push-images 206 rerun_auth_config: 207 github_team_slugs: 208 - org: kubernetes 209 slug: release-managers 210 - org: kubernetes 211 slug: test-infra-admins 212 - org: kubernetes 213 slug: sig-storage-image-build-admins 214 cluster: k8s-infra-prow-build-trusted 215 annotations: 216 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 217 decorate: true 218 decoration_config: 219 timeout: 240m 220 grace_period: 15m 221 branches: 222 # For publishing canary images. 223 - ^master$ 224 - ^release- 225 # For publishing tagged images. Those will only get built once, i.e. 226 # existing images are not getting overwritten. A new tag must be set to 227 # trigger another image build. Images are only built for tags that follow 228 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 229 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 230 spec: 231 serviceAccountName: gcb-builder 232 containers: 233 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 234 command: 235 - /run.sh 236 args: 237 # this is the project GCB will run in, which is the same as the GCR 238 # images are pushed to. 239 - --project=k8s-staging-sig-storage 240 # This is the same as above, but with -gcb appended. 241 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 242 - --env-passthrough=PULL_BASE_REF 243 - . 244 kubernetes-csi/external-resizer: 245 - name: post-external-resizer-push-images 246 rerun_auth_config: 247 github_team_slugs: 248 - org: kubernetes 249 slug: release-managers 250 - org: kubernetes 251 slug: test-infra-admins 252 - org: kubernetes 253 slug: sig-storage-image-build-admins 254 cluster: k8s-infra-prow-build-trusted 255 annotations: 256 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 257 decorate: true 258 decoration_config: 259 timeout: 240m 260 grace_period: 15m 261 branches: 262 # For publishing canary images. 263 - ^master$ 264 - ^release- 265 # For publishing tagged images. Those will only get built once, i.e. 266 # existing images are not getting overwritten. A new tag must be set to 267 # trigger another image build. Images are only built for tags that follow 268 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 269 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 270 spec: 271 serviceAccountName: gcb-builder 272 containers: 273 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 274 command: 275 - /run.sh 276 args: 277 # this is the project GCB will run in, which is the same as the GCR 278 # images are pushed to. 279 - --project=k8s-staging-sig-storage 280 # This is the same as above, but with -gcb appended. 281 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 282 - --env-passthrough=PULL_BASE_REF 283 - . 284 kubernetes-csi/external-snapshotter: 285 - name: post-external-snapshotter-push-images 286 rerun_auth_config: 287 github_team_slugs: 288 - org: kubernetes 289 slug: release-managers 290 - org: kubernetes 291 slug: test-infra-admins 292 - org: kubernetes 293 slug: sig-storage-image-build-admins 294 cluster: k8s-infra-prow-build-trusted 295 annotations: 296 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 297 decorate: true 298 decoration_config: 299 timeout: 240m 300 grace_period: 15m 301 branches: 302 # For publishing canary images. 303 - ^master$ 304 - ^release- 305 # For publishing tagged images. Those will only get built once, i.e. 306 # existing images are not getting overwritten. A new tag must be set to 307 # trigger another image build. Images are only built for tags that follow 308 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 309 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 310 spec: 311 serviceAccountName: gcb-builder 312 containers: 313 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 314 command: 315 - /run.sh 316 args: 317 # this is the project GCB will run in, which is the same as the GCR 318 # images are pushed to. 319 - --project=k8s-staging-sig-storage 320 # This is the same as above, but with -gcb appended. 321 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 322 - --env-passthrough=PULL_BASE_REF 323 - . 324 kubernetes-csi/livenessprobe: 325 - name: post-livenessprobe-push-images 326 rerun_auth_config: 327 github_team_slugs: 328 - org: kubernetes 329 slug: release-managers 330 - org: kubernetes 331 slug: test-infra-admins 332 - org: kubernetes 333 slug: sig-storage-image-build-admins 334 cluster: k8s-infra-prow-build-trusted 335 annotations: 336 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 337 decorate: true 338 decoration_config: 339 timeout: 240m 340 grace_period: 15m 341 branches: 342 # For publishing canary images. 343 - ^master$ 344 - ^release- 345 # For publishing tagged images. Those will only get built once, i.e. 346 # existing images are not getting overwritten. A new tag must be set to 347 # trigger another image build. Images are only built for tags that follow 348 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 349 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 350 spec: 351 serviceAccountName: gcb-builder 352 containers: 353 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 354 command: 355 - /run.sh 356 args: 357 # this is the project GCB will run in, which is the same as the GCR 358 # images are pushed to. 359 - --project=k8s-staging-sig-storage 360 # This is the same as above, but with -gcb appended. 361 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 362 - --env-passthrough=PULL_BASE_REF 363 - . 364 kubernetes-csi/node-driver-registrar: 365 - name: post-node-driver-registrar-push-images 366 rerun_auth_config: 367 github_team_slugs: 368 - org: kubernetes 369 slug: release-managers 370 - org: kubernetes 371 slug: test-infra-admins 372 - org: kubernetes 373 slug: sig-storage-image-build-admins 374 cluster: k8s-infra-prow-build-trusted 375 annotations: 376 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 377 decorate: true 378 decoration_config: 379 timeout: 240m 380 grace_period: 15m 381 branches: 382 # For publishing canary images. 383 - ^master$ 384 - ^release- 385 # For publishing tagged images. Those will only get built once, i.e. 386 # existing images are not getting overwritten. A new tag must be set to 387 # trigger another image build. Images are only built for tags that follow 388 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 389 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 390 spec: 391 serviceAccountName: gcb-builder 392 containers: 393 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 394 command: 395 - /run.sh 396 args: 397 # this is the project GCB will run in, which is the same as the GCR 398 # images are pushed to. 399 - --project=k8s-staging-sig-storage 400 # This is the same as above, but with -gcb appended. 401 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 402 - --env-passthrough=PULL_BASE_REF 403 - . 404 kubernetes-csi/csi-driver-nfs: 405 - name: post-csi-driver-nfs-push-images 406 rerun_auth_config: 407 github_team_slugs: 408 - org: kubernetes 409 slug: release-managers 410 - org: kubernetes 411 slug: test-infra-admins 412 - org: kubernetes 413 slug: sig-storage-image-build-admins 414 cluster: k8s-infra-prow-build-trusted 415 annotations: 416 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 417 decorate: true 418 decoration_config: 419 timeout: 240m 420 grace_period: 15m 421 branches: 422 # For publishing canary images. 423 - ^master$ 424 - ^release- 425 # For publishing tagged images. Those will only get built once, i.e. 426 # existing images are not getting overwritten. A new tag must be set to 427 # trigger another image build. Images are only built for tags that follow 428 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 429 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 430 spec: 431 serviceAccountName: gcb-builder 432 containers: 433 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 434 command: 435 - /run.sh 436 args: 437 # this is the project GCB will run in, which is the same as the GCR 438 # images are pushed to. 439 - --project=k8s-staging-sig-storage 440 # This is the same as above, but with -gcb appended. 441 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 442 - --env-passthrough=PULL_BASE_REF 443 - . 444 kubernetes-csi/csi-driver-iscsi: 445 - name: post-csi-driver-iscsi-push-images 446 rerun_auth_config: 447 github_team_slugs: 448 - org: kubernetes 449 slug: release-managers 450 - org: kubernetes 451 slug: test-infra-admins 452 - org: kubernetes 453 slug: sig-storage-image-build-admins 454 cluster: k8s-infra-prow-build-trusted 455 annotations: 456 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 457 decorate: true 458 decoration_config: 459 timeout: 240m 460 grace_period: 15m 461 branches: 462 # For publishing canary images. 463 - ^master$ 464 - ^release- 465 # For publishing tagged images. Those will only get built once, i.e. 466 # existing images are not getting overwritten. A new tag must be set to 467 # trigger another image build. Images are only built for tags that follow 468 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 469 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 470 spec: 471 serviceAccountName: gcb-builder 472 containers: 473 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 474 command: 475 - /run.sh 476 args: 477 # this is the project GCB will run in, which is the same as the GCR 478 # images are pushed to. 479 - --project=k8s-staging-sig-storage 480 # This is the same as above, but with -gcb appended. 481 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 482 - --env-passthrough=PULL_BASE_REF 483 - . 484 kubernetes-csi/lib-volume-populator: 485 - name: post-lib-volume-populator-push-images 486 rerun_auth_config: 487 github_team_slugs: 488 - org: kubernetes 489 slug: release-managers 490 - org: kubernetes 491 slug: test-infra-admins 492 - org: kubernetes 493 slug: sig-storage-image-build-admins 494 cluster: k8s-infra-prow-build-trusted 495 annotations: 496 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 497 decorate: true 498 decoration_config: 499 timeout: 240m 500 grace_period: 15m 501 branches: 502 # For publishing canary images. 503 - ^master$ 504 - ^release- 505 # For publishing tagged images. Those will only get built once, i.e. 506 # existing images are not getting overwritten. A new tag must be set to 507 # trigger another image build. Images are only built for tags that follow 508 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 509 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 510 spec: 511 serviceAccountName: gcb-builder 512 containers: 513 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 514 command: 515 - /run.sh 516 args: 517 # this is the project GCB will run in, which is the same as the GCR 518 # images are pushed to. 519 - --project=k8s-staging-sig-storage 520 # This is the same as above, but with -gcb appended. 521 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 522 - --env-passthrough=PULL_BASE_REF 523 - . 524 kubernetes-csi/volume-data-source-validator: 525 - name: post-volume-data-source-validator-push-images 526 rerun_auth_config: 527 github_team_slugs: 528 - org: kubernetes 529 slug: release-managers 530 - org: kubernetes 531 slug: test-infra-admins 532 - org: kubernetes 533 slug: sig-storage-image-build-admins 534 cluster: k8s-infra-prow-build-trusted 535 annotations: 536 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 537 decorate: true 538 decoration_config: 539 timeout: 240m 540 grace_period: 15m 541 branches: 542 # For publishing canary images. 543 - ^master$ 544 - ^release- 545 # For publishing tagged images. Those will only get built once, i.e. 546 # existing images are not getting overwritten. A new tag must be set to 547 # trigger another image build. Images are only built for tags that follow 548 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 549 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 550 spec: 551 serviceAccountName: gcb-builder 552 containers: 553 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 554 command: 555 - /run.sh 556 args: 557 # this is the project GCB will run in, which is the same as the GCR 558 # images are pushed to. 559 - --project=k8s-staging-sig-storage 560 # This is the same as above, but with -gcb appended. 561 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 562 - --env-passthrough=PULL_BASE_REF 563 - . 564 kubernetes-sigs/sig-storage-local-static-provisioner: 565 - name: post-sig-storage-local-static-provisioner-push-images 566 rerun_auth_config: 567 github_team_slugs: 568 - org: kubernetes 569 slug: release-managers 570 - org: kubernetes 571 slug: test-infra-admins 572 - org: kubernetes 573 slug: sig-storage-image-build-admins 574 cluster: k8s-infra-prow-build-trusted 575 annotations: 576 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 577 decorate: true 578 decoration_config: 579 timeout: 240m 580 grace_period: 15m 581 branches: 582 # For publishing canary images. 583 - ^master$ 584 - ^release- 585 # For publishing tagged images. Those will only get built once, i.e. 586 # existing images are not getting overwritten. A new tag must be set to 587 # trigger another image build. Images are only built for tags that follow 588 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 589 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 590 spec: 591 serviceAccountName: gcb-builder 592 containers: 593 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 594 command: 595 - /run.sh 596 args: 597 # this is the project GCB will run in, which is the same as the GCR 598 # images are pushed to. 599 - --project=k8s-staging-sig-storage 600 # This is the same as above, but with -gcb appended. 601 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 602 - --env-passthrough=PULL_BASE_REF 603 - . 604 kubernetes-sigs/nfs-ganesha-server-and-external-provisioner: 605 - name: post-nfs-ganesha-server-and-external-provisioner-push-images 606 rerun_auth_config: 607 github_team_slugs: 608 - org: kubernetes 609 slug: release-managers 610 - org: kubernetes 611 slug: test-infra-admins 612 - org: kubernetes 613 slug: sig-storage-image-build-admins 614 cluster: k8s-infra-prow-build-trusted 615 annotations: 616 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 617 decorate: true 618 decoration_config: 619 timeout: 240m 620 grace_period: 15m 621 branches: 622 # For publishing canary images. 623 - ^master$ 624 - ^release- 625 # For publishing tagged images. Those will only get built once, i.e. 626 # existing images are not getting overwritten. A new tag must be set to 627 # trigger another image build. Images are only built for tags that follow 628 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 629 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 630 spec: 631 serviceAccountName: gcb-builder 632 containers: 633 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 634 command: 635 - /run.sh 636 args: 637 # this is the project GCB will run in, which is the same as the GCR 638 # images are pushed to. 639 - --project=k8s-staging-sig-storage 640 # This is the same as above, but with -gcb appended. 641 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 642 - --env-passthrough=PULL_BASE_REF 643 - . 644 kubernetes-sigs/nfs-subdir-external-provisioner: 645 - name: post-nfs-subdir-external-provisioner-push-images 646 rerun_auth_config: 647 github_team_slugs: 648 - org: kubernetes 649 slug: release-managers 650 - org: kubernetes 651 slug: test-infra-admins 652 - org: kubernetes 653 slug: sig-storage-image-build-admins 654 cluster: k8s-infra-prow-build-trusted 655 annotations: 656 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 657 decorate: true 658 decoration_config: 659 timeout: 240m 660 grace_period: 15m 661 branches: 662 # For publishing canary images. 663 - ^master$ 664 - ^release- 665 # For publishing tagged images. Those will only get built once, i.e. 666 # existing images are not getting overwritten. A new tag must be set to 667 # trigger another image build. Images are only built for tags that follow 668 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 669 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 670 spec: 671 serviceAccountName: gcb-builder 672 containers: 673 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 674 command: 675 - /run.sh 676 args: 677 # this is the project GCB will run in, which is the same as the GCR 678 # images are pushed to. 679 - --project=k8s-staging-sig-storage 680 # This is the same as above, but with -gcb appended. 681 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 682 - --env-passthrough=PULL_BASE_REF 683 - . 684 kubernetes-sigs/container-object-storage-interface-controller: 685 - name: post-container-object-storage-interface-controller-push-images 686 rerun_auth_config: 687 github_team_slugs: 688 - org: kubernetes 689 slug: release-managers 690 - org: kubernetes 691 slug: test-infra-admins 692 - org: kubernetes 693 slug: sig-storage-image-build-admins 694 cluster: k8s-infra-prow-build-trusted 695 annotations: 696 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 697 decorate: true 698 decoration_config: 699 timeout: 240m 700 grace_period: 15m 701 branches: 702 # For publishing canary images. 703 - ^master$ 704 - ^release- 705 # For publishing tagged images. Those will only get built once, i.e. 706 # existing images are not getting overwritten. A new tag must be set to 707 # trigger another image build. Images are only built for tags that follow 708 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 709 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 710 spec: 711 serviceAccountName: gcb-builder 712 containers: 713 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 714 command: 715 - /run.sh 716 args: 717 # this is the project GCB will run in, which is the same as the GCR 718 # images are pushed to. 719 - --project=k8s-staging-sig-storage 720 # This is the same as above, but with -gcb appended. 721 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 722 - --env-passthrough=PULL_BASE_REF 723 - . 724 kubernetes-sigs/container-object-storage-interface-provisioner-sidecar: 725 - name: post-container-object-storage-interface-provisioner-sidecar-push-images 726 rerun_auth_config: 727 github_team_slugs: 728 - org: kubernetes 729 slug: release-managers 730 - org: kubernetes 731 slug: test-infra-admins 732 - org: kubernetes 733 slug: sig-storage-image-build-admins 734 cluster: k8s-infra-prow-build-trusted 735 annotations: 736 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 737 decorate: true 738 decoration_config: 739 timeout: 240m 740 grace_period: 15m 741 branches: 742 # For publishing canary images. 743 - ^master$ 744 - ^release- 745 # For publishing tagged images. Those will only get built once, i.e. 746 # existing images are not getting overwritten. A new tag must be set to 747 # trigger another image build. Images are only built for tags that follow 748 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 749 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 750 spec: 751 serviceAccountName: gcb-builder 752 containers: 753 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 754 command: 755 - /run.sh 756 args: 757 # this is the project GCB will run in, which is the same as the GCR 758 # images are pushed to. 759 - --project=k8s-staging-sig-storage 760 # This is the same as above, but with -gcb appended. 761 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 762 - --env-passthrough=PULL_BASE_REF 763 - . 764 kubernetes-csi/csi-proxy: 765 - name: post-csi-proxy-push-images 766 rerun_auth_config: 767 github_team_slugs: 768 - org: kubernetes 769 slug: release-managers 770 - org: kubernetes 771 slug: test-infra-admins 772 - org: kubernetes 773 slug: sig-storage-image-build-admins 774 cluster: k8s-infra-prow-build-trusted 775 annotations: 776 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 777 decorate: true 778 decoration_config: 779 timeout: 240m 780 grace_period: 15m 781 branches: 782 # For publishing canary images. 783 - ^master$ 784 - ^release- 785 # For publishing tagged images. Those will only get built once, i.e. 786 # existing images are not getting overwritten. A new tag must be set to 787 # trigger another image build. Images are only built for tags that follow 788 # the semver format (regex from https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string). 789 - ^v(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\+([0-9a-zA-Z-]+(?:\.[0-9a-zA-Z-]+)*))?$ 790 spec: 791 serviceAccountName: gcb-builder 792 containers: 793 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 794 command: 795 - /run.sh 796 args: 797 # this is the project GCB will run in, which is the same as the GCR 798 # images are pushed to. 799 - --project=k8s-staging-sig-storage 800 # This is the same as above, but with -gcb appended. 801 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 802 - --env-passthrough=PULL_BASE_REF 803 - . 804 805 # Canary images are used by some Prow jobs to ensure that the upcoming releases 806 # of the sidecars work together. We don't promote those canary images. 807 # To avoid getting them evicted from the staging area, we have to rebuild 808 # them periodically. One additional benefit is that build errors show up 809 # in the sig-storage-image-build *before* tagging a release. 810 # 811 # Periodic jobs are currently only specified for the "master" branch 812 # which produces the "canary" images. While other branches 813 # could produce release-x.y-canary images, we don't use those. 814 periodics: 815 - name: canary-csi-driver-host-path-push-images 816 cluster: k8s-infra-prow-build-trusted 817 annotations: 818 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 819 decorate: true 820 interval: 168h # one week 821 extra_refs: 822 # This also becomes the current directory for run.sh and thus 823 # the cloud image build. 824 - org: kubernetes-csi 825 repo: csi-driver-host-path 826 base_ref: master 827 spec: 828 serviceAccountName: gcb-builder 829 containers: 830 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 831 command: 832 - /run.sh 833 env: 834 # We need to emulate a pull job for the cloud build to work the same 835 # way as it usually does. 836 - name: PULL_BASE_REF 837 value: master 838 args: 839 # this is the project GCB will run in, which is the same as the GCR 840 # images are pushed to. 841 - --project=k8s-staging-sig-storage 842 # This is the same as above, but with -gcb appended. 843 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 844 - --env-passthrough=PULL_BASE_REF 845 - . 846 - name: canary-csi-driver-smb-push-images 847 cluster: k8s-infra-prow-build-trusted 848 annotations: 849 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 850 decorate: true 851 interval: 168h # one week 852 extra_refs: 853 # This also becomes the current directory for run.sh and thus 854 # the cloud image build. 855 - org: kubernetes-csi 856 repo: csi-driver-smb 857 base_ref: master 858 spec: 859 serviceAccountName: gcb-builder 860 containers: 861 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 862 command: 863 - /run.sh 864 env: 865 # We need to emulate a pull job for the cloud build to work the same 866 # way as it usually does. 867 - name: PULL_BASE_REF 868 value: master 869 args: 870 # this is the project GCB will run in, which is the same as the GCR 871 # images are pushed to. 872 - --project=k8s-staging-sig-storage 873 # This is the same as above, but with -gcb appended. 874 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 875 - --env-passthrough=PULL_BASE_REF 876 - . 877 - name: canary-csi-test-push-images 878 cluster: k8s-infra-prow-build-trusted 879 annotations: 880 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 881 decorate: true 882 interval: 168h # one week 883 extra_refs: 884 # This also becomes the current directory for run.sh and thus 885 # the cloud image build. 886 - org: kubernetes-csi 887 repo: csi-test 888 base_ref: master 889 spec: 890 serviceAccountName: gcb-builder 891 containers: 892 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 893 command: 894 - /run.sh 895 env: 896 # We need to emulate a pull job for the cloud build to work the same 897 # way as it usually does. 898 - name: PULL_BASE_REF 899 value: master 900 args: 901 # this is the project GCB will run in, which is the same as the GCR 902 # images are pushed to. 903 - --project=k8s-staging-sig-storage 904 # This is the same as above, but with -gcb appended. 905 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 906 - --env-passthrough=PULL_BASE_REF 907 - . 908 - name: canary-external-attacher-push-images 909 cluster: k8s-infra-prow-build-trusted 910 annotations: 911 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 912 decorate: true 913 interval: 168h # one week 914 extra_refs: 915 # This also becomes the current directory for run.sh and thus 916 # the cloud image build. 917 - org: kubernetes-csi 918 repo: external-attacher 919 base_ref: master 920 spec: 921 serviceAccountName: gcb-builder 922 containers: 923 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 924 command: 925 - /run.sh 926 env: 927 # We need to emulate a pull job for the cloud build to work the same 928 # way as it usually does. 929 - name: PULL_BASE_REF 930 value: master 931 args: 932 # this is the project GCB will run in, which is the same as the GCR 933 # images are pushed to. 934 - --project=k8s-staging-sig-storage 935 # This is the same as above, but with -gcb appended. 936 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 937 - --env-passthrough=PULL_BASE_REF 938 - . 939 - name: canary-external-health-monitor-push-images 940 cluster: k8s-infra-prow-build-trusted 941 annotations: 942 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 943 decorate: true 944 interval: 168h # one week 945 extra_refs: 946 # This also becomes the current directory for run.sh and thus 947 # the cloud image build. 948 - org: kubernetes-csi 949 repo: external-health-monitor 950 base_ref: master 951 spec: 952 serviceAccountName: gcb-builder 953 containers: 954 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 955 command: 956 - /run.sh 957 env: 958 # We need to emulate a pull job for the cloud build to work the same 959 # way as it usually does. 960 - name: PULL_BASE_REF 961 value: master 962 args: 963 # this is the project GCB will run in, which is the same as the GCR 964 # images are pushed to. 965 - --project=k8s-staging-sig-storage 966 # This is the same as above, but with -gcb appended. 967 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 968 - --env-passthrough=PULL_BASE_REF 969 - . 970 - name: canary-external-provisioner-push-images 971 cluster: k8s-infra-prow-build-trusted 972 annotations: 973 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 974 decorate: true 975 interval: 168h # one week 976 extra_refs: 977 # This also becomes the current directory for run.sh and thus 978 # the cloud image build. 979 - org: kubernetes-csi 980 repo: external-provisioner 981 base_ref: master 982 spec: 983 serviceAccountName: gcb-builder 984 containers: 985 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 986 command: 987 - /run.sh 988 env: 989 # We need to emulate a pull job for the cloud build to work the same 990 # way as it usually does. 991 - name: PULL_BASE_REF 992 value: master 993 args: 994 # this is the project GCB will run in, which is the same as the GCR 995 # images are pushed to. 996 - --project=k8s-staging-sig-storage 997 # This is the same as above, but with -gcb appended. 998 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 999 - --env-passthrough=PULL_BASE_REF 1000 - . 1001 - name: canary-external-resizer-push-images 1002 cluster: k8s-infra-prow-build-trusted 1003 annotations: 1004 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1005 decorate: true 1006 interval: 168h # one week 1007 extra_refs: 1008 # This also becomes the current directory for run.sh and thus 1009 # the cloud image build. 1010 - org: kubernetes-csi 1011 repo: external-resizer 1012 base_ref: master 1013 spec: 1014 serviceAccountName: gcb-builder 1015 containers: 1016 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1017 command: 1018 - /run.sh 1019 env: 1020 # We need to emulate a pull job for the cloud build to work the same 1021 # way as it usually does. 1022 - name: PULL_BASE_REF 1023 value: master 1024 args: 1025 # this is the project GCB will run in, which is the same as the GCR 1026 # images are pushed to. 1027 - --project=k8s-staging-sig-storage 1028 # This is the same as above, but with -gcb appended. 1029 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1030 - --env-passthrough=PULL_BASE_REF 1031 - . 1032 - name: canary-external-snapshotter-push-images 1033 cluster: k8s-infra-prow-build-trusted 1034 annotations: 1035 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1036 decorate: true 1037 interval: 168h # one week 1038 extra_refs: 1039 # This also becomes the current directory for run.sh and thus 1040 # the cloud image build. 1041 - org: kubernetes-csi 1042 repo: external-snapshotter 1043 base_ref: master 1044 spec: 1045 serviceAccountName: gcb-builder 1046 containers: 1047 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1048 command: 1049 - /run.sh 1050 env: 1051 # We need to emulate a pull job for the cloud build to work the same 1052 # way as it usually does. 1053 - name: PULL_BASE_REF 1054 value: master 1055 args: 1056 # this is the project GCB will run in, which is the same as the GCR 1057 # images are pushed to. 1058 - --project=k8s-staging-sig-storage 1059 # This is the same as above, but with -gcb appended. 1060 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1061 - --env-passthrough=PULL_BASE_REF 1062 - . 1063 - name: canary-livenessprobe-push-images 1064 cluster: k8s-infra-prow-build-trusted 1065 annotations: 1066 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1067 decorate: true 1068 interval: 168h # one week 1069 extra_refs: 1070 # This also becomes the current directory for run.sh and thus 1071 # the cloud image build. 1072 - org: kubernetes-csi 1073 repo: livenessprobe 1074 base_ref: master 1075 spec: 1076 serviceAccountName: gcb-builder 1077 containers: 1078 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1079 command: 1080 - /run.sh 1081 env: 1082 # We need to emulate a pull job for the cloud build to work the same 1083 # way as it usually does. 1084 - name: PULL_BASE_REF 1085 value: master 1086 args: 1087 # this is the project GCB will run in, which is the same as the GCR 1088 # images are pushed to. 1089 - --project=k8s-staging-sig-storage 1090 # This is the same as above, but with -gcb appended. 1091 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1092 - --env-passthrough=PULL_BASE_REF 1093 - . 1094 - name: canary-node-driver-registrar-push-images 1095 cluster: k8s-infra-prow-build-trusted 1096 annotations: 1097 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1098 decorate: true 1099 interval: 168h # one week 1100 extra_refs: 1101 # This also becomes the current directory for run.sh and thus 1102 # the cloud image build. 1103 - org: kubernetes-csi 1104 repo: node-driver-registrar 1105 base_ref: master 1106 spec: 1107 serviceAccountName: gcb-builder 1108 containers: 1109 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1110 command: 1111 - /run.sh 1112 env: 1113 # We need to emulate a pull job for the cloud build to work the same 1114 # way as it usually does. 1115 - name: PULL_BASE_REF 1116 value: master 1117 args: 1118 # this is the project GCB will run in, which is the same as the GCR 1119 # images are pushed to. 1120 - --project=k8s-staging-sig-storage 1121 # This is the same as above, but with -gcb appended. 1122 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1123 - --env-passthrough=PULL_BASE_REF 1124 - . 1125 - name: canary-csi-driver-nfs-push-images 1126 cluster: k8s-infra-prow-build-trusted 1127 annotations: 1128 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1129 decorate: true 1130 interval: 168h # one week 1131 extra_refs: 1132 # This also becomes the current directory for run.sh and thus 1133 # the cloud image build. 1134 - org: kubernetes-csi 1135 repo: csi-driver-nfs 1136 base_ref: master 1137 spec: 1138 serviceAccountName: gcb-builder 1139 containers: 1140 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1141 command: 1142 - /run.sh 1143 env: 1144 # We need to emulate a pull job for the cloud build to work the same 1145 # way as it usually does. 1146 - name: PULL_BASE_REF 1147 value: master 1148 args: 1149 # this is the project GCB will run in, which is the same as the GCR 1150 # images are pushed to. 1151 - --project=k8s-staging-sig-storage 1152 # This is the same as above, but with -gcb appended. 1153 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1154 - --env-passthrough=PULL_BASE_REF 1155 - . 1156 - name: canary-csi-driver-iscsi-push-images 1157 cluster: k8s-infra-prow-build-trusted 1158 annotations: 1159 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1160 decorate: true 1161 interval: 168h # one week 1162 extra_refs: 1163 # This also becomes the current directory for run.sh and thus 1164 # the cloud image build. 1165 - org: kubernetes-csi 1166 repo: csi-driver-iscsi 1167 base_ref: master 1168 spec: 1169 serviceAccountName: gcb-builder 1170 containers: 1171 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1172 command: 1173 - /run.sh 1174 env: 1175 # We need to emulate a pull job for the cloud build to work the same 1176 # way as it usually does. 1177 - name: PULL_BASE_REF 1178 value: master 1179 args: 1180 # this is the project GCB will run in, which is the same as the GCR 1181 # images are pushed to. 1182 - --project=k8s-staging-sig-storage 1183 # This is the same as above, but with -gcb appended. 1184 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1185 - --env-passthrough=PULL_BASE_REF 1186 - . 1187 - name: canary-lib-volume-populator-push-images 1188 cluster: k8s-infra-prow-build-trusted 1189 annotations: 1190 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1191 decorate: true 1192 interval: 168h # one week 1193 extra_refs: 1194 # This also becomes the current directory for run.sh and thus 1195 # the cloud image build. 1196 - org: kubernetes-csi 1197 repo: lib-volume-populator 1198 base_ref: master 1199 spec: 1200 serviceAccountName: gcb-builder 1201 containers: 1202 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1203 command: 1204 - /run.sh 1205 env: 1206 # We need to emulate a pull job for the cloud build to work the same 1207 # way as it usually does. 1208 - name: PULL_BASE_REF 1209 value: master 1210 args: 1211 # this is the project GCB will run in, which is the same as the GCR 1212 # images are pushed to. 1213 - --project=k8s-staging-sig-storage 1214 # This is the same as above, but with -gcb appended. 1215 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1216 - --env-passthrough=PULL_BASE_REF 1217 - . 1218 - name: canary-volume-data-source-validator-push-images 1219 cluster: k8s-infra-prow-build-trusted 1220 annotations: 1221 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1222 decorate: true 1223 interval: 168h # one week 1224 extra_refs: 1225 # This also becomes the current directory for run.sh and thus 1226 # the cloud image build. 1227 - org: kubernetes-csi 1228 repo: volume-data-source-validator 1229 base_ref: master 1230 spec: 1231 serviceAccountName: gcb-builder 1232 containers: 1233 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1234 command: 1235 - /run.sh 1236 env: 1237 # We need to emulate a pull job for the cloud build to work the same 1238 # way as it usually does. 1239 - name: PULL_BASE_REF 1240 value: master 1241 args: 1242 # this is the project GCB will run in, which is the same as the GCR 1243 # images are pushed to. 1244 - --project=k8s-staging-sig-storage 1245 # This is the same as above, but with -gcb appended. 1246 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1247 - --env-passthrough=PULL_BASE_REF 1248 - . 1249 - name: canary-sig-storage-local-static-provisioner-push-images 1250 cluster: k8s-infra-prow-build-trusted 1251 annotations: 1252 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1253 decorate: true 1254 interval: 168h # one week 1255 extra_refs: 1256 # This also becomes the current directory for run.sh and thus 1257 # the cloud image build. 1258 - org: kubernetes-sigs 1259 repo: sig-storage-local-static-provisioner 1260 base_ref: master 1261 spec: 1262 serviceAccountName: gcb-builder 1263 containers: 1264 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1265 command: 1266 - /run.sh 1267 env: 1268 # We need to emulate a pull job for the cloud build to work the same 1269 # way as it usually does. 1270 - name: PULL_BASE_REF 1271 value: master 1272 args: 1273 # this is the project GCB will run in, which is the same as the GCR 1274 # images are pushed to. 1275 - --project=k8s-staging-sig-storage 1276 # This is the same as above, but with -gcb appended. 1277 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1278 - --env-passthrough=PULL_BASE_REF 1279 - . 1280 - name: canary-nfs-ganesha-server-and-external-provisioner-push-images 1281 cluster: k8s-infra-prow-build-trusted 1282 annotations: 1283 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1284 decorate: true 1285 interval: 168h # one week 1286 extra_refs: 1287 # This also becomes the current directory for run.sh and thus 1288 # the cloud image build. 1289 - org: kubernetes-sigs 1290 repo: nfs-ganesha-server-and-external-provisioner 1291 base_ref: master 1292 spec: 1293 serviceAccountName: gcb-builder 1294 containers: 1295 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1296 command: 1297 - /run.sh 1298 env: 1299 # We need to emulate a pull job for the cloud build to work the same 1300 # way as it usually does. 1301 - name: PULL_BASE_REF 1302 value: master 1303 args: 1304 # this is the project GCB will run in, which is the same as the GCR 1305 # images are pushed to. 1306 - --project=k8s-staging-sig-storage 1307 # This is the same as above, but with -gcb appended. 1308 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1309 - --env-passthrough=PULL_BASE_REF 1310 - . 1311 - name: canary-nfs-subdir-external-provisioner-push-images 1312 cluster: k8s-infra-prow-build-trusted 1313 annotations: 1314 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1315 decorate: true 1316 interval: 168h # one week 1317 extra_refs: 1318 # This also becomes the current directory for run.sh and thus 1319 # the cloud image build. 1320 - org: kubernetes-sigs 1321 repo: nfs-subdir-external-provisioner 1322 base_ref: master 1323 spec: 1324 serviceAccountName: gcb-builder 1325 containers: 1326 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1327 command: 1328 - /run.sh 1329 env: 1330 # We need to emulate a pull job for the cloud build to work the same 1331 # way as it usually does. 1332 - name: PULL_BASE_REF 1333 value: master 1334 args: 1335 # this is the project GCB will run in, which is the same as the GCR 1336 # images are pushed to. 1337 - --project=k8s-staging-sig-storage 1338 # This is the same as above, but with -gcb appended. 1339 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1340 - --env-passthrough=PULL_BASE_REF 1341 - . 1342 - name: canary-container-object-storage-interface-controller-push-images 1343 cluster: k8s-infra-prow-build-trusted 1344 annotations: 1345 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1346 decorate: true 1347 interval: 168h # one week 1348 extra_refs: 1349 # This also becomes the current directory for run.sh and thus 1350 # the cloud image build. 1351 - org: kubernetes-sigs 1352 repo: container-object-storage-interface-controller 1353 base_ref: master 1354 spec: 1355 serviceAccountName: gcb-builder 1356 containers: 1357 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1358 command: 1359 - /run.sh 1360 env: 1361 # We need to emulate a pull job for the cloud build to work the same 1362 # way as it usually does. 1363 - name: PULL_BASE_REF 1364 value: master 1365 args: 1366 # this is the project GCB will run in, which is the same as the GCR 1367 # images are pushed to. 1368 - --project=k8s-staging-sig-storage 1369 # This is the same as above, but with -gcb appended. 1370 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1371 - --env-passthrough=PULL_BASE_REF 1372 - . 1373 - name: canary-container-object-storage-interface-provisioner-sidecar-push-images 1374 cluster: k8s-infra-prow-build-trusted 1375 annotations: 1376 testgrid-dashboards: sig-storage-image-build, sig-k8s-infra-gcb 1377 decorate: true 1378 interval: 168h # one week 1379 extra_refs: 1380 # This also becomes the current directory for run.sh and thus 1381 # the cloud image build. 1382 - org: kubernetes-sigs 1383 repo: container-object-storage-interface-provisioner-sidecar 1384 base_ref: master 1385 spec: 1386 serviceAccountName: gcb-builder 1387 containers: 1388 - image: gcr.io/k8s-staging-test-infra/image-builder:v20230711-e33377c2b4 1389 command: 1390 - /run.sh 1391 env: 1392 # We need to emulate a pull job for the cloud build to work the same 1393 # way as it usually does. 1394 - name: PULL_BASE_REF 1395 value: master 1396 args: 1397 # this is the project GCB will run in, which is the same as the GCR 1398 # images are pushed to. 1399 - --project=k8s-staging-sig-storage 1400 # This is the same as above, but with -gcb appended. 1401 - --scratch-bucket=gs://k8s-staging-sig-storage-gcb 1402 - --env-passthrough=PULL_BASE_REF 1403 - .