Skip to content

Remove all reference to gcr.io tekton projects #8885

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 17, 2025
Merged

Remove all reference to gcr.io tekton projects #8885

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions config/300-crds/300-pipelinerun.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2162,7 +2162,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -2239,7 +2239,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -2575,7 +2575,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -2652,7 +2652,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -2862,7 +2862,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -2939,7 +2939,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -5159,7 +5159,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down
12 changes: 6 additions & 6 deletions config/300-crds/300-taskrun.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1738,7 +1738,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -1815,7 +1815,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -2025,7 +2025,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -2102,7 +2102,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -3806,7 +3806,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down Expand Up @@ -4059,7 +4059,7 @@ spec:
description: |-
EntryPoint identifies the entry point into the build. This is often a path to a
build definition file and/or a target label within that file.
Example: "task/git-clone/0.8/git-clone.yaml"
Example: "task/git-clone/0.10/git-clone.yaml"
type: string
uri:
description: |-
Expand Down
2 changes: 1 addition & 1 deletion examples/v1/pipelineruns/beta/git-resolver.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ spec:
- name: url
value: https://github.com/tektoncd/catalog.git
- name: pathInRepo
value: /task/git-clone/0.7/git-clone.yaml
value: /task/git-clone/0.10/git-clone.yaml
- name: revision
value: main
params:
Expand Down
14 changes: 11 additions & 3 deletions examples/v1/pipelineruns/beta/http-resolver-credentials.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,20 +16,28 @@ kind: PipelineRun
metadata:
generateName: http-resolver-
spec:
workspaces:
- name: output
emptyDir: {}
pipelineSpec:
workspaces:
- name: output
tasks:
- name: http-resolver
taskRef:
resolver: http
params:
- name: url
value: https://api.hub.tekton.dev/v1/resource/tekton/task/tkn/0.4/raw
value: https://api.hub.tekton.dev/v1/resource/tekton/task/git-clone/0.10/raw
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be changed to artifacthub.io if the hub is going to be shutdown soon?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. But instead of changing this task, we should probably update the image there to ghcr and use artifacthub.io reference.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can do things in sequence. 0.10 already points to ghcr.io. And the hub api is still up. We will change this in a follow-up. Right now the idea is to get the CI green.

- name: http-username
value: git
- name: http-password-secret
value: my-secret
- name: http-password-secret-key
value: token
params:
- name: ARGS
value: ["version"]
- name: url
value: "https://github.com/kelseyhightower/nocode"
workspaces:
- name: output
workspace: output
14 changes: 11 additions & 3 deletions examples/v1/pipelineruns/beta/http-resolver.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,22 @@ kind: PipelineRun
metadata:
generateName: http-resolver-
spec:
workspaces:
- name: output
emptyDir: {}
pipelineSpec:
workspaces:
- name: output
tasks:
- name: http-resolver
taskRef:
resolver: http
params:
- name: url
value: https://api.hub.tekton.dev/v1/resource/tekton/task/tkn/0.4/raw
value: https://api.hub.tekton.dev/v1/resource/tekton/task/git-clone/0.10/raw
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be changed to artifacthub.io if the hub is going to be shutdown soon?

params:
- name: ARGS
value: ["version"]
- name: url
value: "https://github.com/kelseyhightower/nocode"
workspaces:
- name: output
workspace: output
2 changes: 1 addition & 1 deletion examples/v1/pipelineruns/no-ci/git-resolver-custom-apiurl.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ spec:
- name: url
value: https://github.com/tektoncd/catalog.git
- name: pathInRepo
value: /task/git-clone/0.7/git-clone.yaml
value: /task/git-clone/0.10/git-clone.yaml
- name: revision
value: main
# my-secret-token should be created in the namespace where the
Expand Down
2 changes: 1 addition & 1 deletion examples/v1/pipelineruns/no-ci/git-resolver-custom-secret.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ spec:
- name: url
value: https://github.com/tektoncd/catalog.git
- name: pathInRepo
value: /task/git-clone/0.7/git-clone.yaml
value: /task/git-clone/0.10/git-clone.yaml
- name: revision
value: main
# my-secret-token should be created in the namespace where the
Expand Down
4 changes: 2 additions & 2 deletions examples/v1/pipelineruns/pipelinerun-with-final-tasks.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ spec:
description: The precise commit SHA that was fetched by this Task
steps:
- name: clone
image: gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init:latest
image: ghcr.io/tektoncd-catalog/git-clone:v1.1.0
securityContext:
runAsUser: 0 # This needs root, and git-init is nonroot by default
script: |
Expand Down Expand Up @@ -200,4 +200,4 @@ spec:
resources:
requests:
storage: 1Gi
---
---
4 changes: 2 additions & 2 deletions examples/v1/pipelineruns/pipelinerun.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ spec:
description: The precise commit SHA that was fetched by this Task
steps:
- name: clone
image: gcr.io/tekton-releases/github.com/tektoncd/pipeline/cmd/git-init:latest
image: ghcr.io/tektoncd-catalog/git-clone:v1.1.0
securityContext:
runAsUser: 0 # This needs root, and git-init is nonroot by default
script: |
Expand Down Expand Up @@ -223,4 +223,4 @@ spec:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
storage: 1Gi
2 changes: 1 addition & 1 deletion examples/v1/taskruns/authenticating-git-commands.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,7 @@ spec:
git commit -m "Test commit!"
git push origin master
- name: git-clone-and-check
image: gcr.io/tekton-releases/dogfooding/alpine-git-nonroot:latest
image: ghcr.io/tektoncd/plumbing/alpine-git-nonroot:latest
# Because this Step runs with a non-root security context, the creds-init
# credentials will fail to copy into /tekton/home. This happens because
# our previous step _already_ wrote to /tekton/home and ran as a root
Expand Down
2 changes: 1 addition & 1 deletion examples/v1/taskruns/beta/authenticating-git-commands.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,7 @@ spec:
git commit -m "Test commit!"
git push origin master
- name: git-clone-and-check
image: gcr.io/tekton-releases/dogfooding/alpine-git-nonroot:latest
image: ghcr.io/tektoncd/plumbing/alpine-git-nonroot:latest
# Because this Step runs with a non-root security context, the creds-init
# credentials will fail to copy into /tekton/home. This happens because
# our previous step _already_ wrote to /tekton/home and ran as a root
Expand Down
2 changes: 1 addition & 1 deletion examples/v1/taskruns/beta/bundles-resolver.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ spec:
resolver: bundles
params:
- name: bundle
value: gcr.io/tekton-releases/catalog/upstream/git-clone@sha256:8e2c3fb0f719d6463e950f3e44965aa314e69b800833e29e68ba2616bb82deeb
value: ghcr.io/tektoncd/catalog/upstream/tasks/git-clone@sha256:65e61544c5870c8828233406689d812391735fd4100cb444bbd81531cb958bb3 # 0.10 bundle
- name: name
value: git-clone
- name: kind
Expand Down
2 changes: 1 addition & 1 deletion examples/v1/taskruns/beta/git-resolver.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,4 +22,4 @@ spec:
- name: revision
value: main
- name: pathInRepo
value: task/git-clone/0.8/git-clone.yaml
value: task/git-clone/0.10/git-clone.yaml
4 changes: 2 additions & 2 deletions examples/v1/taskruns/beta/hub-resolver.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ spec:
- name: name
value: git-clone
- name: version
value: "0.6"
value: "0.10"
---
apiVersion: tekton.dev/v1
kind: TaskRun
Expand All @@ -48,4 +48,4 @@ spec:
- name: name
value: git-clone
- name: version
value: "0.6.0"
value: "0.10"
2 changes: 1 addition & 1 deletion examples/v1/taskruns/entrypoint-resolution.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ spec:
# Multi-arch image with no command defined. We should look up the command
# for each platform-specific image and pass it to the Pod, which selects
# the right command at runtime based on the node's runtime platform.
- image: gcr.io/tekton-nightly/github.com/tektoncd/pipeline/cmd/nop
- image: ghcr.io/tektoncd/pipeline/nop-8eac7c133edad5df719dc37b36b62482:latest

# Multi-arch image with no command defined, but with args. We'll look
# up the commands and pass it to the entrypoint binary via env var, then
Expand Down
2 changes: 1 addition & 1 deletion examples/v1/taskruns/no-ci/docker-creds.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,6 @@ spec:
taskSpec:
steps:
- name: test
image: gcr.io/tekton-releases/dogfooding/skopeo:latest
image: ghcr.io/tektoncd/catalog/upstream/tasks/skopeo-copy:latest
# Test pulling a private builder container.
script: skopeo copy docker://gcr.io/build-crd-testing/secret-sauce dir:///tmp/
2 changes: 1 addition & 1 deletion examples/v1/taskruns/no-ci/pull-private-image.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,5 +47,5 @@ spec:
steps:
- name: pull
# Private image is just Ubuntu
image: gcr.io/tekton-releases/dogfooding/skopeo:latest
image: ghcr.io/tektoncd/catalog/upstream/tasks/skopeo-copy:latest
script: skopeo copy docker://gcr.io/build-crd-testing/secret-sauce dir:///tmp/
2 changes: 1 addition & 1 deletion pkg/apis/pipeline/v1/openapi_generated.go
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion pkg/apis/pipeline/v1/provenance.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,6 @@ type RefSource struct {

// EntryPoint identifies the entry point into the build. This is often a path to a
// build definition file and/or a target label within that file.
// Example: "task/git-clone/0.8/git-clone.yaml"
// Example: "task/git-clone/0.10/git-clone.yaml"
EntryPoint string `json:"entryPoint,omitempty"`
}
2 changes: 1 addition & 1 deletion pkg/apis/pipeline/v1/swagger.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1185,7 +1185,7 @@
}
},
"entryPoint": {
"description": "EntryPoint identifies the entry point into the build. This is often a path to a build definition file and/or a target label within that file. Example: \"task/git-clone/0.8/git-clone.yaml\"",
"description": "EntryPoint identifies the entry point into the build. This is often a path to a build definition file and/or a target label within that file. Example: \"task/git-clone/0.10/git-clone.yaml\"",
"type": "string"
},
"uri": {
Expand Down
4 changes: 2 additions & 2 deletions pkg/apis/pipeline/v1beta1/openapi_generated.go
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions pkg/apis/pipeline/v1beta1/provenance.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ type RefSource struct {

// EntryPoint identifies the entry point into the build. This is often a path to a
// build definition file and/or a target label within that file.
// Example: "task/git-clone/0.8/git-clone.yaml"
// Example: "task/git-clone/0.10/git-clone.yaml"
EntryPoint string `json:"entryPoint,omitempty"`
}

Expand All @@ -62,6 +62,6 @@ type ConfigSource struct {

// EntryPoint identifies the entry point into the build. This is often a path to a
// build definition file and/or a target label within that file.
// Example: "task/git-clone/0.8/git-clone.yaml"
// Example: "task/git-clone/0.10/git-clone.yaml"
EntryPoint string `json:"entryPoint,omitempty"`
}
4 changes: 2 additions & 2 deletions pkg/apis/pipeline/v1beta1/swagger.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -306,7 +306,7 @@
}
},
"entryPoint": {
"description": "EntryPoint identifies the entry point into the build. This is often a path to a build definition file and/or a target label within that file. Example: \"task/git-clone/0.8/git-clone.yaml\"",
"description": "EntryPoint identifies the entry point into the build. This is often a path to a build definition file and/or a target label within that file. Example: \"task/git-clone/0.10/git-clone.yaml\"",
"type": "string"
},
"uri": {
Expand Down Expand Up @@ -1592,7 +1592,7 @@
}
},
"entryPoint": {
"description": "EntryPoint identifies the entry point into the build. This is often a path to a build definition file and/or a target label within that file. Example: \"task/git-clone/0.8/git-clone.yaml\"",
"description": "EntryPoint identifies the entry point into the build. This is often a path to a build definition file and/or a target label within that file. Example: \"task/git-clone/0.10/git-clone.yaml\"",
"type": "string"
},
"uri": {
Expand Down
2 changes: 1 addition & 1 deletion tekton/release-pipeline.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ spec:
- name: name
value: git-clone
- name: version
value: "0.7"
value: "0.10"
workspaces:
- name: output
workspace: workarea
Expand Down
Loading
Loading