Skip to content

Conversation

@anithapriyanatarajan
Copy link
Contributor

Changes

This pull request updates the Tekton release cheat sheet and release pipeline to reflect new infrastructure and workflow changes, primarily switching from Google Cloud (GCP) to Oracle Cloud Infrastructure (OCI) and updating release URLs. The changes standardize release parameters, update secret and bucket references, and revise instructions for interacting with clusters and release files.

Infrastructure and URL updates:

  • Changed all release file and bucket URLs from storage.googleapis.com to infra.tekton.dev, ensuring consistency with the new hosting location.
  • Updated cluster authentication instructions from using gcloud (GCP) to OCI CLI commands, reflecting the migration to Oracle Cloud.

Parameter and secret updates:

  • Adjusted pipeline start parameters by removing obsolete ones (e.g., serviceaccount, serviceAccountPath), adding repoName, and updating secret references from release-secret to oci-release-secret where appropriate.

Release workflow improvements:

  • Updated instructions for fetching controller image SHA and Rekor UUID to use the new release file URLs and improved parsing commands for compatibility.
  • Added guidance for renaming the Kubernetes context using the current context name, making it easier to follow for users unfamiliar with GCP context naming.

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • pre-commit Passed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

/kind misc

@tekton-robot tekton-robot added kind/misc Categorizes issue or PR as a miscellaneuous one. release-note-none Denotes a PR that doesnt merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Dec 1, 2025
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 1, 2025
@anithapriyanatarajan
Copy link
Contributor Author

Need this to be on hold until the PRs in plumbing repos related to this PR are merged. Will update the details here shortly

@afrittoli
Copy link
Member

Need this to be on hold until the PRs in plumbing repos related to this PR are merged. Will update the details here shortly

Could you include a link to said PRs please?

@anithapriyanatarajan
Copy link
Contributor Author

Need this to be on hold until the PRs in plumbing repos related to this PR are merged. Will update the details here shortly

Could you include a link to said PRs please?

@afrittoli Please review - tektoncd/plumbing#2948

@vdemeester
Copy link
Member

The plumbing PR is now merged 👼🏼

@tekton-robot tekton-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Dec 2, 2025
@anithapriyanatarajan anithapriyanatarajan changed the title WIP: chore(release-pipeline): update references to oci bucket chore(release-pipeline): update references to oci bucket Dec 2, 2025
@tekton-robot tekton-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 2, 2025
@anithapriyanatarajan
Copy link
Contributor Author

@vdemeester @afrittoli - Thankyou. Updated release pipeline and cheatsheet with the prcheck task and upload tasks poiting the latest plumbing and catalog versions. Please review

@afrittoli
Copy link
Member

/retest

Copy link
Member

@afrittoli afrittoli left a comment

Choose a reason for hiding this comment

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

/approve

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: afrittoli

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 3, 2025
Comment on lines +175 to +177
```
Sample secret template for reference:
```
Copy link
Member

Choose a reason for hiding this comment

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

NIT: missing new-lines

kubectl apply -f tekton/account.yaml
kubectl patch serviceaccount $ACCOUNT \
-p "{\"secrets\": [{\"name\": \"$GENERIC_SECRET\"}]}"
1. When executing release pipelines, some tasks require `oci cli` commands. The CLI requires credentials which should be created as a Kubernetes secret and mounted to the respective task's workspace. For example refer the precheck definition.
Copy link
Member

Choose a reason for hiding this comment

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

NIT: It's ok to explain this, as it may be handy for troubleshooting.
The cheat-sheet should be an operational guide to what needs to be done step by step to make a release. The secret is deployed to the cluster via terraform, so the release manager should not need to create the secret.

TEKTON_OLD_VERSION= # Example: v0.68.0
TEKTON_RELEASE_NAME="Oriental Longhair Omnibot" # Name of the release
TEKTON_PACKAGE=tektoncd/pipeline
TEKTON_REPO_NAME=pipeline
Copy link
Member

Choose a reason for hiding this comment

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

NIT: Why do we need this here? The repo name is already set to the valid default in the pipeline.

Copy link
Contributor Author

@anithapriyanatarajan anithapriyanatarajan Dec 3, 2025

Choose a reason for hiding this comment

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

This is a needed for release-draft-oci pipeline that is called from plumbing repo.

@vdemeester
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2025
@vdemeester vdemeester merged commit 478d30f into tektoncd:main Dec 3, 2025
78 of 87 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in Tekton Community Roadmap Dec 3, 2025
--param releaseBucket=gs://tekton-releases/pipeline \
--param releaseBucket=tekton-releases \
--param koExtraArgs="" \
--workspace name=release-secret,secret=release-secret \
Copy link
Member

Choose a reason for hiding this comment

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

This should be oci-release-secret

```bash
RELEASE_FILE=https://storage.googleapis.com/tekton-releases/pipeline/previous/${TEKTON_VERSION}/release.yaml
CONTROLLER_IMAGE_SHA=$(curl $RELEASE_FILE | egrep 'ghcr.io.*controller' | cut -d'@' -f2)
RELEASE_FILE=https://infra.tekton.dev/tekton-releases/triggers/previous/${VERSION_TAG}/release.yaml
Copy link
Member

Choose a reason for hiding this comment

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

VERSION_TAG is not defined, it should be TEKTON_VERSION as it was before

Copy link
Member

Choose a reason for hiding this comment

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

The project is not triggers, it should be pipeline as it was

Create a pod template file:

```shell
cat <<EOF > tekton/pod-template.yaml
Copy link
Member

Choose a reason for hiding this comment

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

This writes the file to tekton/pod-template.yaml and right after tries to get the file as pod-template.yaml (without the folder). Could you change this to pod-template instead?

We could add this file and the workspace one to .gitignore or we could do something like:

POD_TEMPLATE=$(mktemp)
cat <<EOF > $POD_TEMPLATE

(...)

--pod-template "${POD_TEMPLATE}" \

for both files

Optional: Add a photo of this release's "purr programmer" (someone's cat).

1. Update [the catalog repo](https://github.com/tektoncd/catalog) test infrastructure
to use the new release by updating the `RELEASE_YAML` link in [e2e-tests.sh](https://github.com/tektoncd/catalog/blob/main/test/e2e-tests.sh).
Copy link
Member

Choose a reason for hiding this comment

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

I forgot to update this in the past, perhaps you could update it as well?

1. Update [the catalog repo](https://github.com/tektoncd/catalog) test infrastructure
to use the new release by updating the test matrix in the `[ci.yaml](https://github.com/tektoncd/catalog/blob/main/.github/workflows/ci.yaml)`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants