Skip to content

fix: remove release-right-meow SA from PAC release PipelineRuns#3336

Merged
tekton-robot merged 1 commit intotektoncd:mainfrom
vdemeester:remove-release-sa
Apr 8, 2026
Merged

fix: remove release-right-meow SA from PAC release PipelineRuns#3336
tekton-robot merged 1 commit intotektoncd:mainfrom
vdemeester:remove-release-sa

Conversation

@vdemeester
Copy link
Copy Markdown
Member

Changes

Remove the release-right-meow ServiceAccount from the PAC release
PipelineRuns (.tekton/release.yaml and .tekton/release-patch.yaml).

This SA is a leftover from the old EventListener-based release flow on
the GKE cluster. On the Oracle cluster, all release secrets (OCI bucket,
GHCR, GitHub token) are mounted as workspaces directly in the
PipelineRun, so no special SA permissions are needed. The default
ServiceAccount in the releases-operator namespace is sufficient.

Without this fix, release PipelineRuns fail at the first task with:

serviceaccounts "release-right-meow" not found

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

NONE

/kind bug

@tekton-as-code
Copy link
Copy Markdown

tekton-as-code bot commented Apr 7, 2026

Caution

There are some errors in your PipelineRun template.

PipelineRun Error
release-pipeline CEL expression evaluation error: expression "has(body.created) && body.created == true && pac.target_branch.startsWith(\"refs/heads/release-v\")\n" check failed: ERROR: <input>:1:46: undeclared reference to 'pac' (in container '') | has(body.created) && body.created == true && pac.target_branch.startsWith("refs/heads/release-v") | .............................................^

@tekton-robot tekton-robot added kind/bug Categorizes issue or PR as related to a bug. release-note-none Denotes a PR that doesnt merit a release note. labels Apr 7, 2026
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 7, 2026
@jkhelil
Copy link
Copy Markdown
Member

jkhelil commented Apr 7, 2026

/approve

@tekton-robot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkhelil

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 Apr 7, 2026
Fix the on-cel-expression to use the correct CEL variables:
- Use 'event' and 'target_branch' (not 'pac.target_branch' which is
  only available in {{ cel: }} param substitution, not in
  on-cel-expression matching)
- Use 'target_branch' without 'refs/heads/' prefix (PAC strips it)
- Use '|' literal block scalar instead of '>' folding to avoid
  trailing newline issues
- Add 'event == "push"' for explicitness

Also remove the release-right-meow ServiceAccount from both
PipelineRuns. It is a leftover from the old EventListener-based
release flow. All release secrets are mounted as workspaces, so
the default SA is sufficient.
@tekton-robot tekton-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Apr 7, 2026
@jkhelil
Copy link
Copy Markdown
Member

jkhelil commented Apr 8, 2026

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2026
@tekton-robot tekton-robot merged commit 3c00e60 into tektoncd:main Apr 8, 2026
16 checks passed
@vdemeester vdemeester deleted the remove-release-sa branch April 8, 2026 08:00
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/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants