<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rollout Example :: Ay Docs</title>
    <link>https://ops.docs.72602.space/kubernetes/serverless/kserve/canary/example/index.html</link>
    <description>Create the InferenceService Follow the First Inference Service tutorial. Set up a namespace kserve-test and create an InferenceService.&#xA;After rolling out the first model, 100% traffic goes to the initial model with service revision 1.&#xA;kubectl -n kserve-test get isvc sklearn-iris Expectd Output NAME URL READY PREV LATEST PREVROLLEDOUTREVISION LATESTREADYREVISION AGE sklearn-iris http://sklearn-iris.kserve-test.example.com True 100 sklearn-iris-predictor--00001 46s 2m39s 70s Apply Canary Rollout Strategy Add the canaryTrafficPercent field to the predictor component Update the storageUri to use a new/updated model. kubectl apply -n kserve-test -f - &lt;&lt;EOF apiVersion: &#34;serving.kserve.io/v1beta1&#34; kind: &#34;InferenceService&#34; metadata: name: &#34;sklearn-iris&#34; namespace: kserve-test spec: predictor: canaryTrafficPercent: 10 model: args: [&#34;--enable_docs_url=True&#34;] modelFormat: name: sklearn resources: {} runtime: kserve-sklearnserver storageUri: &#34;gs://kfserving-examples/models/sklearn/1.0/model-2&#34; EOF After rolling out the canary model, traffic is split between the latest ready revision 2 and the previously rolled out revision 1.</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate></lastBuildDate>
    <atom:link href="https://ops.docs.72602.space/kubernetes/serverless/kserve/canary/example/index.xml" rel="self" type="application/rss+xml" />
  </channel>
</rss>