-
Notifications
You must be signed in to change notification settings - Fork 426
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
Comments
Unfortunately, I don't think this is an officially supported feature. However, you could modify your Tekton Triggers controller deployment called "-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. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
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. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
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)
The text was updated successfully, but these errors were encountered: