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

Add KEDA support to seldon-core #2506

Merged
merged 7 commits into from
Oct 15, 2020
Merged

Conversation

anggao
Copy link
Contributor

@anggao anggao commented Sep 30, 2020

What this PR does / why we need it:
Add KEDA support to seldon-core

Which issue(s) this PR fixes:

Fixes #2498

Special notes for your reviewer:
As part of this work, I also upgraded golang version to 1.14 as this is required for knative.dev/pkg module used by KEDA

Does this PR introduce a user-facing change?:

Added KEDA support to seldon-core

@seldondev
Copy link
Collaborator

Hi @anggao. Thanks for your PR.

I'm waiting for a SeldonIO member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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 jenkins-x/lighthouse repository.

@anggao
Copy link
Contributor Author

anggao commented Sep 30, 2020

/assign @cliveseldon

@ukclivecox
Copy link
Contributor

@anggao Can you add an example notebook to illustrate in the /examples folder?

@ukclivecox
Copy link
Contributor

/ok-to-test

@seldondev
Copy link
Collaborator

Thu Oct 1 10:52:07 UTC 2020
The logs for [lint] [2] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/2.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=2

@seldondev
Copy link
Collaborator

Thu Oct 1 10:52:14 UTC 2020
The logs for [pr-build] [1] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/1.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=1

@anggao
Copy link
Contributor Author

anggao commented Oct 1, 2020

sure I will do and fix the tests

@anggao
Copy link
Contributor Author

anggao commented Oct 1, 2020

/retest

@seldondev
Copy link
Collaborator

Thu Oct 1 15:34:38 UTC 2020
The logs for [lint] [4] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/4.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=4

@seldondev
Copy link
Collaborator

Thu Oct 1 15:34:41 UTC 2020
The logs for [pr-build] [3] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/3.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=3

@anggao
Copy link
Contributor Author

anggao commented Oct 1, 2020

@cliveseldon can I run these tests locally ?

@ukclivecox
Copy link
Contributor

The CI steps are defined at top level of project. The failed on would be: https://github.com/SeldonIO/seldon-core/blob/master/jenkins-x.yml

Not sure why lint is pending.

You can run locally these steps. See what they do in the jenkins definitions

@seldondev
Copy link
Collaborator

Fri Oct 2 11:32:01 UTC 2020
The logs for [pr-build] [5] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/5.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=5

@seldondev
Copy link
Collaborator

Fri Oct 2 11:32:18 UTC 2020
The logs for [lint] [6] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/6.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=6

@seldondev
Copy link
Collaborator

Fri Oct 2 11:46:16 UTC 2020
The logs for [lint] [8] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/8.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=8

@seldondev
Copy link
Collaborator

Fri Oct 2 11:46:14 UTC 2020
The logs for [pr-build] [7] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/7.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=7

@anggao
Copy link
Contributor Author

anggao commented Oct 2, 2020

@cliveseldon I added example and fixed the build

@seldondev
Copy link
Collaborator

Fri Oct 2 17:21:04 UTC 2020
The logs for [lint] [10] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/10.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=10

@seldondev
Copy link
Collaborator

Fri Oct 2 17:21:16 UTC 2020
The logs for [pr-build] [9] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/9.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=9

@ukclivecox
Copy link
Contributor

/test integration

@seldondev
Copy link
Collaborator

Tue Oct 6 12:40:38 UTC 2020
The logs for [integration] [11] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/11.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=11

@seldondev
Copy link
Collaborator

Tue Oct 6 13:14:04 UTC 2020
The logs for [lint] [13] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/13.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=13

@seldondev
Copy link
Collaborator

Tue Oct 6 13:14:06 UTC 2020
The logs for [pr-build] [12] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/12.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=12

@ukclivecox
Copy link
Contributor

I don't see changes to split_resources for the new helm value, e.g. addition to

HELM_ENV_SUBST = {
"AMBASSADOR_ENABLED": "ambassador.enabled",
"AMBASSADOR_SINGLE_NAMESPACE": "ambassador.singleNamespace",
"ENGINE_SERVER_GRPC_PORT": "engine.grpc.port",
"ENGINE_CONTAINER_IMAGE_PULL_POLICY": "engine.image.pullPolicy",
"ENGINE_LOG_MESSAGES_EXTERNALLY": "engine.logMessagesExternally",
"ENGINE_SERVER_PORT": "engine.port",
"ENGINE_PROMETHEUS_PATH": "engine.prometheus.path",
"ENGINE_CONTAINER_USER": "engine.user",
"ENGINE_CONTAINER_SERVICE_ACCOUNT_NAME": "engine.serviceAccount.name",
"ISTIO_ENABLED": "istio.enabled",
"ISTIO_GATEWAY": "istio.gateway",
"ISTIO_TLS_MODE": "istio.tlsMode",
"PREDICTIVE_UNIT_SERVICE_PORT": "predictiveUnit.port",
"PREDICTIVE_UNIT_DEFAULT_ENV_SECRET_REF_NAME": "predictiveUnit.defaultEnvSecretRefName",
"PREDICTIVE_UNIT_METRICS_PORT_NAME": "predictiveUnit.metricsPortName",
"USE_EXECUTOR": "executor.enabled",
"EXECUTOR_CONTAINER_IMAGE_PULL_POLICY": "executor.image.pullPolicy",
"EXECUTOR_SERVER_PORT": "executor.port",
"EXECUTOR_SERVER_METRICS_PORT_NAME": "executor.metricsPortName",
"EXECUTOR_PROMETHEUS_PATH": "executor.prometheus.path",
"EXECUTOR_CONTAINER_USER": "executor.user",
"EXECUTOR_CONTAINER_SERVICE_ACCOUNT_NAME": "executor.serviceAccount.name",
"MANAGER_CREATE_RESOURCES": "managerCreateResources",
"EXECUTOR_REQUEST_LOGGER_DEFAULT_ENDPOINT": "executor.requestLogger.defaultEndpoint",
"DEFAULT_USER_ID": "defaultUserID",
}

@seldondev
Copy link
Collaborator

Mon Oct 12 13:54:04 UTC 2020
The logs for [pr-build] [35] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/35.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=35

@seldondev
Copy link
Collaborator

Mon Oct 12 13:54:13 UTC 2020
The logs for [lint] [36] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/36.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=36

@seldondev
Copy link
Collaborator

Mon Oct 12 14:00:00 UTC 2020
The logs for [lint] [38] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/38.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=38

@seldondev
Copy link
Collaborator

Mon Oct 12 14:00:00 UTC 2020
The logs for [pr-build] [37] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/37.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=37

@ukclivecox
Copy link
Contributor

/test notebooks

@ukclivecox
Copy link
Contributor

/approve

@seldondev
Copy link
Collaborator

Mon Oct 12 14:24:41 UTC 2020
The logs for [notebooks] [39] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/39.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=39

@anggao
Copy link
Contributor Author

anggao commented Oct 12, 2020

/retest

@RafalSkolasinski
Copy link
Contributor

@anggao the test in question (that tests custom metrics) seems to have passed in other PR that was also failing
Could you please make sure you are rebased onto master and then trigger the notebook tests again?

@seldondev
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cliveseldon

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@seldondev
Copy link
Collaborator

Wed Oct 14 18:26:32 UTC 2020
The logs for [lint] [41] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/41.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=41

@seldondev
Copy link
Collaborator

Wed Oct 14 18:26:32 UTC 2020
The logs for [pr-build] [40] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/40.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=40

@anggao
Copy link
Contributor Author

anggao commented Oct 14, 2020

@RafalSkolasinski sure just did it

@anggao
Copy link
Contributor Author

anggao commented Oct 14, 2020

/test notebooks

@seldondev
Copy link
Collaborator

Wed Oct 14 18:29:26 UTC 2020
The logs for [notebooks] [42] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2506/42.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2506 --build=42

@seldondev
Copy link
Collaborator

@anggao: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
notebooks ce0d57b link /test notebooks

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 jenkins-x/lighthouse repository. I understand the commands that are listed here.

@ukclivecox ukclivecox merged commit dd3f71f into SeldonIO:master Oct 15, 2020
@ukclivecox
Copy link
Contributor

Thanks @groszewn ! We will investigate flaky tests in master.

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

Successfully merging this pull request may close these issues.

Add KEDA support for seldon-core
5 participants