Skip to content
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.

[WIP] Experimental KEDA support for Kafka Event Source #886

Closed
wants to merge 12 commits into from

Conversation

aslom
Copy link
Member

@aslom aslom commented Feb 4, 2020

Warning: this is experimental and may be changed in future. Should not be used in production. This is mainly for discussion and evolving scaling in Knative eventing.

The code is using Unstructured and also imported KEDA API - this is for discussion which version should be used (right now only Unstructured is fully implemented).
KEDA to provide client-go support discussion #494 kedacore/keda#494

Release Note

Experimental KEDA support for Kafka Event Source

@knative-prow-robot knative-prow-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 4, 2020
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Feb 4, 2020
@knative-prow-robot knative-prow-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Feb 4, 2020
@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

1 similar comment
@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no Indicates the PR's author has not signed the CLA. and removed cla: yes Indicates the PR's author has signed the CLA. labels Feb 4, 2020
@lberk
Copy link
Member

lberk commented Feb 4, 2020

I assume we'll also want to include a finalizer, or some mechanism to ensure we delete the scaled objects we created/own as we delete the kafkasource itself?

@aslom
Copy link
Member Author

aslom commented Feb 4, 2020

@lberk for cleanup using OwnerReferences should allow to automatically delete ScaledObject if owner of it is KafkaSource without need to do finalizer?

@zroubalik
Copy link

@lberk for cleanup using OwnerReferences should allow to automatically delete ScaledObject if owner of it is KafkaSource without need to do finalizer?

yeah, it should be like that

@knative-prow-robot knative-prow-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Feb 14, 2020
@aslom
Copy link
Member Author

aslom commented Feb 14, 2020

@googlebot I fixed it.

@aslom aslom changed the title [WIP] Experimental KEDA support for Kafka Event Source Experimental KEDA support for Kafka Event Source Feb 19, 2020
@aslom aslom changed the title Experimental KEDA support for Kafka Event Source WIP Experimental KEDA support for Kafka Event Source Feb 19, 2020
@aslom aslom changed the title WIP Experimental KEDA support for Kafka Event Source [WIP] Experimental KEDA support for Kafka Event Source Feb 20, 2020
Copy link
Member

@mattmoor mattmoor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Produced via:
prettier --write --prose-wrap=always $(find -name '*.md' | grep -v vendor | grep -v .github | grep -v docs/cmd/)

Co-Authored-By: Matt Moore <mattmoor@vmware.com>
Copy link
Member

@mattmoor mattmoor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Produced via:
prettier --write --prose-wrap=always $(find -name '*.md' | grep -v vendor | grep -v .github | grep -v docs/cmd/)

kafka/source/README.md Outdated Show resolved Hide resolved
Co-Authored-By: Matt Moore <mattmoor@vmware.com>
Co-Authored-By: Matt Moore <mattmoor@vmware.com>
@knative-prow-robot
Copy link
Contributor

knative-prow-robot commented Mar 27, 2020

@aslom: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-knative-eventing-contrib-build-tests 9339051 link /test pull-knative-eventing-contrib-build-tests

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 12, 2020
@knative-prow-robot
Copy link
Contributor

@aslom: PR needs rebase.

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.

@matzew
Copy link
Member

matzew commented Jun 25, 2020

Is this in sync with the work that @zroubalik is proposing?

Or should we close this ?

@aslom
Copy link
Member Author

aslom commented Jun 25, 2020

@matzew I am checking with @zroubalik

@zroubalik
Copy link

I am using a separate controller and not using this stuff. I'd like to present the initial work on the next week WG or the week after (I have a conflict that time, so it's not that easy for me to join).
I'd keep this open until I show my proposal and then we can choose which direction we would like to go.

@aslom
Copy link
Member Author

aslom commented Jun 29, 2020

I have chatted with Zbynek and it seems his approach is more general and may work better. After he presented it to WG then I am going to close this issue.

@duglin
Copy link

duglin commented Jun 29, 2020

cool - looking forward to seeing it.

@matzew
Copy link
Member

matzew commented Jul 23, 2020

@aslom with the new doc you presented in the WG, should we close this now ?

@zroubalik
Copy link

On the latest WG I have proposed this approach: https://github.com/zroubalik/autoscaler-keda

I think we can close this one.

@aslom
Copy link
Member Author

aslom commented Jul 24, 2020

Yes. Closing it for ow as we explore other options: knative/eventing#2901 (comment)

@aslom aslom closed this Jul 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes Indicates the PR's author has signed the CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants