[Triggers] Add a EventListener port-forward command
Open
Nobody has claimed this yet.
kind/feature
- Dominant language
- Go
- Stars
- 461
- Forks
- 277
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 95
Description
Feature request
It would be nice to have a tkn command to port-forward to an EventListener.
Currently, users have to use kubectl directly and either have to find the pod that the eventlistener creates or rely on a naming convention that Triggers uses to create EventListener services.
kubectl port-forward service/el-my-listener 8080:8080
OR
kubectl port-forward \
"$(kubectl get pod --selector=eventlistener=github-listener-interceptor -oname)" \
8000
Use case
- Locally testing/debugging/invoking a Trigger in an EventListener
UI Example
tkn eventlistener port-forward my-listener -n namespace
tkn eventlistener port-forward my-listener -n namespace -p 9001 #optional port
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 at the proposed tkn eventlistener port-forward command entry point and compare the kubectl service and pod port-forward examples in the issue. Done means an EventListener can be selected by name and namespace, an optional local port is supported, and the command enables local testing or invocation of its Trigger.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100