Dev Task: OC use bound tokens
- Dominant language
- Python
- Stars
- 65
- Forks
- 11
- Avg merge
- 21h 25m
- Merged PRs (30d)
- 70
Description
**Describe the task**
Our deployment pipeline has this warning: Warning: Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
**Acceptance Criteria**
- [ ] All GH pipelines are using bound tokens
**Additional context**
- https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#manually-create-a-long-lived-api-token-for-a-serviceaccount
Contributor guide
Research direction
Start by reviewing all GitHub pipelines and locating where service-account tokens are configured. Use the linked Kubernetes TokenRequest guidance to determine the bound-token approach, then verify that every pipeline uses bound tokens and the warning is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100