Upgrading Knative
How to upgrade knative for Seldon Deploy.
seldonio/rclone-storage-initializer
which requires adjustment of credential secret. It is also possible to fallback to kfserving/storage-initializer
that will work with previous secret format. Please consult our documentation for more details.metadata.pg.enabled
false in your values file then you don’t need to configure anything for request logger metadata lookup.metadata.pg.enabled
to false in the values file (though this also disables metadata) or set requestLogger.deployHost
and requestLogger.authSecret
to emptymetadata.pg.enabled
in the Seldon Deploy helm chart to false
.
Not recommended since all model metadata related features will be unavailable.metadata-postgres
secret in the Seldon Deploy namespace (instructions).metadata.pg.enabled
in the Seldon Deploy helm chart to true
(instructions).seldon-logs
namespace and into the user namespaces. To handle this
kubectl get ksvc -n seldon-logs
. Also check kubectl get trigger -n seldon-logs
.-outlier
, -drift
or -metrics
in their names. Each will have a ksvc
and a corresponding trigger
. The name and namespace of the model they are for will also be in the name.elasticsearch.basicAuth
flag in the Seldon Deploy Helm chart.<= 1.1.0
), you can set its value as elasticsearch.basicAuth=false
.1.7.0
. See the Getting Started > Production Installation
section for installation. A helm upgrade --install
can be used to upgrade.gs://seldon-models/alibi-detect/cd/ks/cifar10-0_4_3
to gs://seldon-models/alibi-detect/cd/ks/cifar10-0_4_4
. This is because the alibi version in Seldon Core is upgraded.prometheus.server.livenessProbePeriodSeconds
is now 30prometheus.server.extraArgs
has been added with entries query.max-concurrency: 400
and storage.remote.read-concurrent-limit: 30
prometheus.server.resources.limits
now has cpu: 2
and memory: 4Gi
prometheus.server.resources.requests
now has cpu: 800m
and memory: 1Gi
helm delete -n seldon-system seldon-core-analytics
.The recommended seldon deploy helm values have changed slightly to improve performance. Set the following:
resources.limits
should now have cpu: 800m
and memory: 800Mi
A further change to the seldon deploy helm values is the addition of a configuration for the runAsUser for knative pods started by deploy:
defaultUserID: "8888"
dockercreds.txt
is now called sdconfig.txt
(anyone using Product Installation
can ignore this).
KUBEFLOW_USER_EMAIL
has become SD_USER_EMAIL
and KUBEFLOW_PASSWORD
has become SD_PASSWORD
Getting Started > Production Installation
Getting Started > Production Installation
section on Argo
and refer to references to .requestLogger.image
in the helm values file is now docker.io/seldonio/seldon-request-logger:1.5.0
alibidetect.image
in the helm values is now seldonio/alibi-detect-server:1.5.0
.batchjobs
section of the helm values - serviceAccount: "workflow"
Getting Started > Production Installation
section for installation.Getting Started > Production Installation > Metrics Monitoring
seldon-deploy-install/prerequisites-setup/prometheus/seldon-core-analytics.sh
from the scripts extracted in Getting Started > Download Installation Resources
.requestLogger.image
in the helm values file is now docker.io/seldonio/seldon-request-logger:1.3.0-json
requestLogger.trigger
in the helm values now has apiVersion
“eventing.knative.dev/v1” and broker
“default”.alibidetect.image
in the helm values is now seldonio/alibi-detect-server:1.4.0
.batchjobs
section in the helm values.The helm values file now has a single gitops section. This involves the following changes.
The sd-install-default script contains an example of this. It is:
kubectl create secret generic git-creds -n seldon-system --from-file ~/.ssh/id_rsa --from-file ~/.ssh/known_hosts --from-literal=passphrase="$GIT_SSHKEY_PASSPHRASE" --from-literal=username="$GIT_USER" --from-literal=token="$GIT_TOKEN" --from-literal=email="$GIT_EMAIL" --dry-run -o yaml | kubectl apply -f -
skipVerifyGit, gitwebhook, GITOPS_FORMAT and argocd config have all moved from github
to the new gitops
section in helm values file, see documentation.
if your ArgoCD Application does not follow naming pattern seldon-gitops-${namespace}
, please, specify the ArgoCD application using namespace labels, see documentation.
The contents of the helm chart have also changed. In particular:
/seldon-deploy/api/status
How to upgrade knative for Seldon Deploy.