-
Notifications
You must be signed in to change notification settings - Fork 420
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
add tolerations to eventlistener #597
add tolerations to eventlistener #597
Conversation
|
Hi @GwonsooLee. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/assign @vtereso |
Hi, @GwonsooLee Thanks for the PR! This looks related to #505 Could you add a |
@dibyom Thanks for review. I added |
/ok-to-test |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
@@ -5,6 +5,12 @@ metadata: | |||
name: listener | |||
spec: | |||
serviceAccountName: tekton-triggers-example-sa | |||
# podTemplate: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a separate example of eventlistener with tolerations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @GwonsooLee In addition to an example like @khrm mentioned, could we add some docs to this as well :
https://github.com/tektoncd/triggers/blob/master/docs/eventlisteners.md#syntax
Also, before we can merge we'd have to squash the commits!
go.mod
Outdated
@@ -13,7 +13,9 @@ require ( | |||
github.com/google/go-github/v31 v31.0.0 | |||
github.com/gorilla/mux v1.7.3 | |||
github.com/grpc-ecosystem/grpc-gateway v1.13.0 // indirect | |||
github.com/onsi/ginkgo v1.10.2 // indirect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm...any idea why this got added 🤔 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it was added indirectly when I ran dependency script. I ran e2e test without it and it worked so that I removed it.
test/eventlistener_scale_test.go
Outdated
bldr.EventListenerPodTemplate( | ||
bldr.EventListenerPodTemplateSpec( | ||
bldr.EventListenerPodTemplateTolerations(nil), | ||
// If you want to test toleration feature, please use this commented part. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the test commented out because it will fail in our CI runs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No.. it worked even though I uncommented it. I commented out those lines because I think test process cannot verify it really works because I guess there is no tainted node for e2e test. I uncommented every lines about tolerations in test files.
test/eventlistener_test.go
Outdated
bldr.EventListenerPodTemplate( | ||
bldr.EventListenerPodTemplateSpec( | ||
bldr.EventListenerPodTemplateTolerations(nil), | ||
// If you want to test toleration feature, please use this commented part. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question as above...is this failing in CI? If it is and it is really hard to test this on our current e2e setup, we can open an issue for it. But I think I'd prefer not having commented out bits of code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left comment above! 👍
57a3c9d
to
64771af
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/test all |
The following is the coverage report on the affected files.
|
64771af
to
52a4cb6
Compare
The following is the coverage report on the affected files.
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
Just needs a rebase to resolve the go.mod conflicts |
52a4cb6
to
d94724c
Compare
The following is the coverage report on the affected files.
|
d94724c
to
98375b8
Compare
98375b8
to
41d4fdd
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/test pull-tekton-triggers-build-tests |
I rebase master and I ran though e2e test.. but build test failed.. @dibyom, could you please let me know what I've been doing wrong..? I will try to figure out too! Thanks you in advance.. |
The problem is :
Its strange that this popped up in this PR given that this line was not touched 🤔 |
Running gosec locally does not fail with this problem either 😕 |
/test pull-tekton-triggers-build-tests |
Should be fixed by https://github.com/tektoncd/triggers/pull/620/files |
/test pull-tekton-triggers-build-tests |
It seems a bug in gosec. Thank you so much for fixing this problem! 👍 |
/lgtm |
/test pull-tekton-triggers-integration-tests |
Changes
Add
tolerations
to eventlistener. This is needed when I want to make event listener to the tainted node.Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Release Notes