

# only. Leave blank if using account/key or MSI.--rclone_config_az_use_msi="" \ # use a managed service identity to

# authenticate (only works in Azure).

--rclone_config_az_client_id="" \ # client ID of the service principal

# to use for authentication.

--rclone_config_az_client_secret="" \ # client secret of the service

# principal to use for authentication.

--rclone_config_az_tenant="" \ # tenant ID of the service principal

# to use for authentication.

# Alternatively for providing key-value pairs, you can utilize the '--values' option by specifying a file path containing

# key-value pairs in either JSON or YAML format.

# File content example: {"rclone_config_az_type":"azureblob",...}

zenml secret create az-seldon-secret \

--values=@path/to/file.json

How do you use it?

Requirements

To run pipelines that deploy models to Seldon, you need the following tools installed locally:

Docker

K3D (can be installed by running curl -s https://raw.githubusercontent.com/rancher/k3d/main/install.sh | bash).

Stack Component Registration

For registering the model deployer, we need the URL of the Istio Ingress Gateway deployed on the Kubernetes cluster. We can get this URL by running the following command (assuming that the service name is istio-ingressgateway, deployed in the istio-system namespace):

# For GKE clusters, the host is the GKE cluster IP address.

export INGRESS_HOST=$(kubectl -n istio-system get service istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}')

# For EKS clusters, the host is the EKS cluster IP hostname.

export INGRESS_HOST=$(kubectl -n istio-system get service istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].hostname}')

Now register the model deployer: