Skip to content

Commit

Permalink
Change the sha for the nop image
Browse files Browse the repository at this point in the history
The sha for the nop image started returning 500 errors.
Pulling the image via the tag "latest" works and returns a different
sha, so updating our config to use the working one.
  • Loading branch information
afrittoli authored and tekton-robot committed May 29, 2020
1 parent 58c836d commit ea3e72e
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion config/controller.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,8 @@ spec:
"-build-gcs-fetcher-image", "github.com/tektoncd/pipeline/vendor/github.com/GoogleCloudPlatform/cloud-builders/gcs-fetcher/cmd/gcs-fetcher",

# These images are pulled from Dockerhub, by digest, as of May 19, 2020.
"-nop-image", "tianon/true@sha256:183cb5fd54142948ad88cc986a217465cfe8786cfdd89b1ed1fc49825da413a7",
# As of May 29, 2020 new sha for nop image
"-nop-image", "tianon/true@sha256:009cce421096698832595ce039aa13fa44327d96beedb84282a69d3dbcf5a81b",
# This is google/cloud-sdk:293.0.0-slim
"-gsutil-image", "google/cloud-sdk@sha256:37654ada9b7afbc32828b537030e85de672a9dd468ac5c92a36da1e203a98def",
# The shell image must be root in order to create directories and copy files to PVCs.
Expand Down

0 comments on commit ea3e72e

Please sign in to comment.