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

Roll out model with istio #1823

Merged
merged 6 commits into from
Oct 22, 2018
Merged

Roll out model with istio #1823

merged 6 commits into from
Oct 22, 2018

Conversation

lluunn
Copy link
Contributor

@lluunn lluunn commented Oct 19, 2018

Separate the service part (model) and the deployment (version) of TF serving.

To serve a model, we should deploy service + deployment as:

Service

ks generate tf-serving-service mnist-service
ks param set mnist-service modelName mnist
ks param set mnist-service trafficRule v1:100    // optional, it's the default value

Deployment

ks generate tf-serving-deployment-gcp mnist-v1
ks param set mnist-v1 modelName mnist
ks param set mnist-v1 versionName v1   // optional, it's the default value
ks param set mnist-v1  modelBasePath gs://kubeflow-examples-data/mnist
ks param set mnist-v1 gcpCredentialSecretName user-gcp-sa
ks param set mnist-v1 injectIstio true

To rollout the version v2,

ks generate tf-serving-deployment-gcp mnist-v2
ks param set mnist-v2 modelName mnist
ks param set mnist-v2 versionName v2
ks param set mnist-v2  modelBasePath gs://kubeflow-examples-data/mnist
ks param set mnist-v2 gcpCredentialSecretName user-gcp-sa
ks param set mnist-v2 injectIstio true
// traffic split
ks param set mnist-service trafficRule v1:50,v2:50

/cc @jlewi

related:
#1309


This change is Reviewable

"apiVersion: ambassador/v0",
"kind: Mapping",
"name: tfserving-predict-mapping-" + modelName,
"prefix: /tfserving/models/" + modelName,
Copy link
Contributor

Choose a reason for hiding this comment

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

We don't need to address it in this PR; but do we need to have individual rewrite rules for different paths and methods?

Could we just have a single rewrite rule
/tfserving/models/modelName -> /v1/models/

@jlewi
Copy link
Contributor

jlewi commented Oct 22, 2018

This is great. Thanks.

/lgtm
/approve

Can you resolve the conflicts?

@lluunn
Copy link
Contributor Author

lluunn commented Oct 22, 2018

test comment

@k8s-ci-robot k8s-ci-robot removed the lgtm label Oct 22, 2018
@lluunn
Copy link
Contributor Author

lluunn commented Oct 22, 2018

test comment

@jlewi
Copy link
Contributor

jlewi commented Oct 22, 2018

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlewi

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

@k8s-ci-robot k8s-ci-robot merged commit 6fee47a into kubeflow:master Oct 22, 2018
saffaalvi pushed a commit to StatCan/kubeflow that referenced this pull request Feb 11, 2021
* roll out model with istio

* fix test

* fix test

* fix test

* fix test
surajkota pushed a commit to surajkota/kubeflow that referenced this pull request Jun 13, 2022
* application path update: certmanager, istio, authservice

* application path update: certmanager, istio, kfserving, knative

* delete deprecated/unused component

application path update: namespace, roles, katib, central dashboard

* application path update: notebook, tensorboard, mpi, xgboost...

* application path update: dex, mxnet, kfp-argo

* add kfp-tekton to ibm distribution

update oidc appid to create secret for clientId and secret
move kubeflow istio resources to own application folder

* ibm 1.3 kfdef

* change kubeflow istio resources to own applicaiton

* add fixed nodeport for istio ingressgateway

* Don't overwrite all namespaces to kubeflow

* add kfdef for ibm kubeflow 1.3

add dex for single user
add oauthservice for dex

* add new line at end of file

* kfdef reporef name fix

* kfdef reporef kustomization fix

* add moficodes and pvaneck to IBM distribution owners

remove adrian555 from IBM Distribution owners

* add kfserving to kfdef

* remove duplicate compononet from kfdef

* reorder profile component

profile crds need to be created before we try to create profile instance

Co-authored-by: Tommy Li <Tommy.chaoping.li@ibm.com>
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.

4 participants