tektoncd / tektoncd/operator

ServiceAccount for Pruner is missing on install

Open
#3,130 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug
Dominant language
Go
Stars
608
Forks
263
Avg merge
1d 3h
Merged PRs (30d)
125

Description

Expected Behavior

Pruner is running.

Actual Behavior

Error events from the tekton-pipelines namespace: Error creating: pods "tekton-resource-pruner-8nvxx-29436900-" is forbidden: error looking up service account tekton-pipelines/tekton-resource-pruner: serviceaccount "tekton-resource-pruner" not found.

And from the default namespace: Internal error occurred: failed calling webhook "validation.webhook.pruner.tekton.dev.global": failed to call webhook: Post "https://tekton-pruner-webhook.tekton-pipelines.svc:443/validate-configmap?timeout=5s": service "tekton-pruner-webhook" not found

Steps to Reproduce the Problem

  1. Fresh install using kubectl apply -f https://infra.tekton.dev/tekton-releases/operator/previous/v0.78.1/release.yaml

Additional Info

  • Kubernetes version: k3s

    Output of kubectl version:

Client Version: v1.33.6+k3s1
Kustomize Version: v5.6.0
Server Version: v1.33.6+k3s1
  • Tekton Pipeline version:

    Output of tkn version or kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}': v1.6.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the fresh install with the referenced v0.78.1 release.yaml and inspect the installed resources in the tekton-pipelines namespace. The fix is complete when the pruner ServiceAccount and webhook service are created and Pruner runs without the reported errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.