predictor_2 = V1beta1PredictorSpec(tensorflow=V1beta1TFServingSpec(storage_uri=storage_uri,
                                                                         image=image),
                                        min_replicas=1,
                                        max_replicas=3,
                                        canary_traffic_percent=50,
                                       )

isvc_2 = V1beta1InferenceService(api_version="serving.kubeflow.org/v1beta1",
                          kind=constants.KFSERVING_KIND,
                          metadata=client.V1ObjectMeta(name=predictor_name, namespace=namespace),
                          spec=V1beta1InferenceServiceSpec(predictor=predictor_2))

kfs.replace(name=predictor_name, inferenceservice=isvc_2, namespace=namespace)

(base) jovyan@tensorboard-normal-0:~$ k get InferenceService
NAME     URL                                    READY   PREV   LATEST   PREVROLLEDOUTREVISION   LATESTREADYREVISION              AGE
demo   http://demo.test-ns.example.com          True           100                              demo-predictor-default-5sn57   8m59s

In reply to@_slack_kubeflow_U0253V66WCT:matrix.org
By the way, if I use different storage_uri , it will replace or patch successfully, but we are using TFX. Pusher, a component of TFX, saves trained-model under a folder, e.g., ./models/1, /models/2, … we need to specify the storage_uri to the ./models level for loading saved model of TF. In this case, kfserving won’t do replace or patch. Does any possible way to deal with it?

In reply to@_slack_kubeflow_UFVUV2UFP:matrix.org
Yulong that's by design, if the storage uri is not changed then nothing is deployed as we want to make storage immutable. But I think in this case you can add an annotation to indicate the version change then InferenceService will redeploy and load the correct version

In reply to@_slack_kubeflow_UFVUV2UFP:matrix.org
Any change should be surfaced on inference service yaml which is the whole point of declarative deployment

Error creating: Internal error occurred: failed calling webhook "inferenceservice.kserve-webhook-server.pod-mutator": Post "https://kserve-webhook-server-service.kserve.
svc:443/mutate-pods?timeout=10s": x509: certificate is not valid for any names, but wanted to match kserve-webhook-server-service.kserve.svc

In reply to@_slack_kubeflow_US7RRCDL2:matrix.org
We're currently upgrading our stg cluster to kserve 0.7 and I'm seeing

Error creating: Internal error occurred: failed calling webhook "inferenceservice.kserve-webhook-server.pod-mutator": Post "https://kserve-webhook-server-service.kserve.
svc:443/mutate-pods?timeout=10s": x509: certificate is not valid for any names, but wanted to match kserve-webhook-server-service.kserve.svc

At the replicaset . I tried to delete the TLS secret but that hasn't resolved the issue. Just wanted to see if anyone could help point us to how to correctly configure the secret. Thanks,

In reply to@_slack_kubeflow_US7RRCDL2:matrix.org
Looks related to this issue: https://github.com/kserve/kserve/issues/1749

apiVersion: cert-manager.io/v1alpha3
kind: Certificate
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: ,
      {"apiVersion":"cert-manager.io/v1alpha2","kind":"Certificate","metadata":{"annotations":{},"labels":{"argocd.argoproj.io/instance":"kfserving-ms-stg"},"name":"serving-cert","namespace":"kserve"},"spec":{"commonName":"kserve-webhook-ser
ver-service.kserve.svc","dnsNames":["kserve-webhook-server-service.kserve.svc"],"issuerRef":{"kind":"Issuer","name":"selfsigned-issuer"},"secretName":"kserve-webhook-server-cert"}}
  creationTimestamp: "2021-10-18T20:55:47Z"
  generation: 1
  labels:
    argocd.argoproj.io/instance: kfserving-ms-stg
  name: serving-cert
  namespace: kserve
  resourceVersion: "274549132"
  uid: 670ad7e7-2b79-4b26-986f-59f83faba216
spec:
  commonName: kserve-webhook-server-service.kserve.svc
  dnsNames:
  - kserve-webhook-server-service.kserve.svc
  issuerRef:
    kind: Issuer
    name: selfsigned-issuer
  secretName: kserve-webhook-server-cert
status:
  conditions:
  - lastTransitionTime: "2021-10-18T20:55:47Z"
    message: Certificate is up to date and has not expired
    reason: Ready
    status: "True"
    type: Ready
  notAfter: "2022-01-16T20:55:47Z"