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

[wip] smi scaler #783

Closed
wants to merge 2 commits into from
Closed

[wip] smi scaler #783

wants to merge 2 commits into from

Conversation

adnxn
Copy link

@adnxn adnxn commented Apr 26, 2020

addresses #615

adnan added 2 commits April 25, 2020 23:58
ran `make generate-api`

Signed-off-by: adnan <adnan.khan021@gmail.com>
Signed-off-by: adnan <adnan.khan021@gmail.com>
@adnxn
Copy link
Author

adnxn commented Apr 28, 2020

will reopen with changes from #787

@adnxn adnxn closed this Apr 28, 2020
@zroubalik
Copy link
Member

zroubalik commented Apr 28, 2020

@adnxn just be aware that client-go PR is opened for v2 branch, we are about to release KEDA v2 with some changes in ScaledObject and other internal modifications.

@zroubalik
Copy link
Member

@adnxn v2 is based on kubernetes-17.4 so you might want to build your scaler on that. The only downside is that v2 will be release later (my guess is June/July)

@adnxn
Copy link
Author

adnxn commented Apr 28, 2020

right - i think it would make sense to just include those changes and refactor this PR to account for the changes in ScaledObject

@tomkerkhove
Copy link
Member

I'm wondering if we should use v2 or v1? Wouldn't it make sense to use it for v1 for now and replatting it with the rest or is the effort too high?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants