-
Notifications
You must be signed in to change notification settings - Fork 17
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
Fix: example manager and instructions #48
Fix: example manager and instructions #48
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #48 +/- ##
==========================================
- Coverage 75.23% 73.30% -1.93%
==========================================
Files 12 15 +3
Lines 1078 1195 +117
==========================================
+ Hits 811 876 +65
- Misses 229 275 +46
- Partials 38 44 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Please sign the DCO with |
@@ -5,7 +5,9 @@ metadata: | |||
creationTimestamp: null | |||
name: kube-trigger-manager-role | |||
rules: | |||
- resources: | |||
- apiGroups: |
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 this file is auto generated, can you help to check that is there anything wrong with the generator? cc @charlie0129
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.
Yes, that's right. Maybe newer versions of kubectl
require apiGroups
to be set.
I fixed the generator to generate that field in the latest commit.
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.
Great job!
Can you sign the DCO? There are instuctions if you click on Details
on DCO check.
Hey @FogDong and @charlie0129 |
Hey |
I tried following the DCO fix guide but I'm getting errors referring to signatures from other contributers I checked out the PR following the linked guide and it seems I pulled all the changes from the PR in my branch 😕 |
You can use With your branch back to the original state, then you can solve the DCO. |
0a617ff
to
69bc6f6
Compare
* Feat: upgrade k8s.io dependency to 0.26 Signed-off-by: Yin Da <yd219913@alibaba-inc.com> * Fix: golangci-lint action failure Signed-off-by: Yin Da <yd219913@alibaba-inc.com> --------- Signed-off-by: Yin Da <yd219913@alibaba-inc.com> Signed-off-by: Amit Singh <singhamitch@outlook.com>
Feat: add cluster info in action context Signed-off-by: yangsoon <songyang.song@alibaba-inc.com> Co-authored-by: yangsoon <songyang.song@alibaba-inc.com> Signed-off-by: Amit Singh <singhamitch@outlook.com>
* Refactor: allow the use of singleton for one Source, while also allowing non-singleton Sources, making it more extensible Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * Feat: add cronjob source Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * Chore: update cron lib Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * Feat: do not exit if config contains invalid sources Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * Chore: add tests and fix linter Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * Chore: go mod tidy Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * Docs: add cronjob example Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * fix comments Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * Chore: force lint to use the exact version Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * remove unnecessary dep Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * fix comments Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * use codecov token Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> * update lint script Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> --------- Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com> Signed-off-by: Amit Singh <singhamitch@outlook.com>
Signed-off-by: yangsoon <songyang.song@alibaba-inc.com> Co-authored-by: yangsoon <songyang.song@alibaba-inc.com> Signed-off-by: Amit Singh <singhamitch@outlook.com>
Signed-off-by: Amit Singh <singhamitch@outlook.com>
Signed-off-by: Amit Singh <singhamitch@outlook.com>
Signed-off-by: Amit Singh <singhamitch@outlook.com>
Signed-off-by: Amit Singh <singhamitch@outlook.com>
69bc6f6
to
3d37b0d
Compare
Thanks a lot @charlie0129 |
The code changes doesn't seem right. It contains many unrelated changes. |
Can I reset back to commit b76f491? |
3d37b0d
to
b76f491
Compare
4895b15
to
b358fd1
Compare
@charlie0129 I've removed all the unrelated changes and all the commits are signed too. |
Great work! Thanks @semmet95 ! |
Description of your changes
Updated ClusterRole and Quick Start guide.
Fixes #47
Fixes #
rules[0].apiGroups: Required value: resource rules must supply at least one api group
error.I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
By running the quick tutorial with the updated examples.
Special notes for your reviewer
I have updated the Quick Start guide's Prerequisites section to including enabling the
kube-trigger
addon