How to set the TEKTON_RESULTS_API_SERVICE value of the watcher deployment via the operator config
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
The TEKTON_RESULTS_API_SERVICE env. value in the watcher deployment is set to the fixed value tekton-results-api-service.tekton-pipelines.svc.cluster.local:8080. This won't work if you use a custom k8s cluster domain name. Is there a possibility to override this value with the Tekton operator that deploys the Tekton results parts?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the operator configures the watcher deployment and where the fixed TEKTON_RESULTS_API_SERVICE value is set. Check how a custom Kubernetes cluster domain could be represented in that configuration. Done means the watcher can receive a configurable service value instead of relying on the fixed cluster domain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100