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

Provide an PredicetKube scaler #2458

Closed
daniel-yavorovich opened this issue Jan 10, 2022 · 5 comments · Fixed by #2418
Closed

Provide an PredicetKube scaler #2458

daniel-yavorovich opened this issue Jan 10, 2022 · 5 comments · Fixed by #2418

Comments

@daniel-yavorovich
Copy link
Contributor

Proposal

PredictKube is a proactive KEDA scaler made by Dysnix for Kubernetes projects

Scaler Source

Prometheus + PredictKube AI API

Scaling Mechanics

It's based on an AI model trained on cloud traffic data: public, business, and custom metrics. It helps to deal with overprovisioning by predicting the traffic trend and timely resource balancing. PredictKube is easy to install in your environment and its AI model demands only 2 weeks data about your traffic to start predicting efficiently.

Authentication Source

API key

Anything else?

We'd like to develop this project continuously, and thus, we encourage you to leave us your feedback. We're eager to hear your thoughts about PredictKube and its model efficiency.

Related PR: #2418

@tomkerkhove tomkerkhove changed the title Provide an PredicrtKube scaler Provide an PredicetKube scaler Jan 10, 2022
@tomkerkhove
Copy link
Member

Relates to #197 & #2401

@tomkerkhove
Copy link
Member

Can you share some more information related to the billing model & legal implications of PredictKube? For example, will you train the AI model based on the metrics that you use for KEDA?

@tomkerkhove
Copy link
Member

Also, our community standup is next week on Tuesday. Would you be able to join it and share more on this scaler?

@daniel-yavorovich
Copy link
Contributor Author

Can you share some more information related to the billing model & legal implications of PredictKube? For example, will you train the AI model based on the metrics that you use for KEDA?

Hi Tom. Thank you for your questions. Regarding the legal issues of PredictKube, we can assure that:
Any personal data that we are asking for is used only for sending the API key and contacting our representatives to answer the questions about PredictKube. We may ask for the name, email address, company name, phone number—so people choose a way to communicate with us that is convenient for them.
We store log files and collect data about the performance of a PredictKube in a certain environment. But we do not monitor or log data from customer servers when they use PredictKube, as we may collect only statuses and logs of the PredictKube itself. And also we have access to typical web analytics of PredictKube website including the type of browser, access sessions, pages views, IP address, and the page visited before entering our website.
We track the metrics of KEDA on the basis of a third-party service provider.
We’re sorry for publishing Cookies and Privacy Policies earlier. They’ll be published soon, and I’ll add a link here for everyone to review it.
Here’s an answer about the billing model. Free access to the PredictKube will be available on a permanent basis, and we’ll constantly pay attention to updating and developing this tool. Thus, users will be able to make predictions based on a generic AI model. Later on, we plan to add a Business paid plan for those who want to train their own model on specific data. But this part of the service is only in development for now.

@daniel-yavorovich
Copy link
Contributor Author

Also, our community standup is next week on Tuesday. Would you be able to join it and share more on this scaler?

we will be happy to join you, tell you about PredictKube, and answer all your questions!

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

Successfully merging a pull request may close this issue.

2 participants