Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change event listener port #586

Closed
sebgoa opened this issue May 27, 2020 · 5 comments · Fixed by #881
Closed

Change event listener port #586

sebgoa opened this issue May 27, 2020 · 5 comments · Fixed by #881
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@sebgoa
Copy link

sebgoa commented May 27, 2020

question:

Is it possible to change the event listener port ?

Right now it serves on 8080, I would like to change it to 80. Editing the services and setting the port does not work (I guess the controller is overriding it)

@ncskier
Copy link
Member

ncskier commented May 28, 2020

Unfortunately, I don't think this is an officially supported feature. However, you could modify your Tekton Triggers controller deployment called tekton-triggers-controller to change the -el-port to 80:

          "-el-port", "8080",

I don't think that this has been thoroughly tested, so I'll mark this issue as a feature request 👍

/kind feature

This is related to #505, which is also about customizing the EventListener Service/Deployment.

@tekton-robot tekton-robot added the kind/feature Categorizes issue or PR as related to a new feature. label May 28, 2020
@tekton-robot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 14, 2020
@tekton-robot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@dibyom dibyom reopened this Aug 14, 2020
@dibyom dibyom removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 8, 2020
@tekton-robot
Copy link

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.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 7, 2020
@dibyom dibyom removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2020
@dibyom dibyom linked a pull request Dec 30, 2020 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants