cli
cli copied to clipboard
tektoncd
[Triggers] Add a EventListener port-forward command
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
I would be interested to work on this! Do you think it's fair for this to be a very stripped down version of kubectl in the sense that only 1 port can be specified and the local port will be the same as the remote port?
Yes, I do not think it is necessary to support all the different options that kubectl supports. However, I think we should support the different local port options to prevent collisions in case the user has something running on that local port already.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
