Production Environment
Install Core 2 in a production Kubernetes environment.
Prerequisites
Set up and connect to a Kubernetes cluster running version 1.27 or later. For instructions on connecting to your Kubernetes cluster, refer to the documentation provided by your cloud provider.
Install kubectl, the Kubernetes command-line tool.
Install Helm, the package manager for Kubernetes.
To use Seldon Core 2 in a production environment:
Seldon publishes the Helm charts that are required to install Seldon Core 2. For more information about the Helm charts and the related dependencies, see Helm charts and Dependencies.
Creating Namespaces
Create a namespace to contain the main components of Seldon Core 2. For example, create the namespace
seldon-mesh
:Create a namespace to contain the components related to monitoring. For example, create the namespace
seldon-monitoring
:
Installing Seldon Core 2
Add and update the Helm charts
seldon-charts
to the repository.Install custom resource definitions for Seldon Core 2.
Install Seldon Core 2 operator in the
seldon-mesh
namespace.This configuration installs the Seldon Core 2 operator across an entire Kubernetes cluster. To perform cluster-wide operations, create
ClusterRoles
and ensure your user has the necessary permissions during deployment. With cluster-wide operations, you can createSeldonRuntimes
in any namespace.You can configure the installation to deploy the Seldon Core 2 operator in a specific namespace so that it control resources in the provided namespace. To do this, set
controller.clusterwide
tofalse
.Install Seldon Core 2 runtimes in the namespace
seldon-mesh
.Install Seldon Core 2 servers in the namespace
seldon-mesh
. Two example servers namedmlserver-0
, andtriton-0
are installed so that you can load the models to these servers after installation.Check Seldon Core 2 operator, runtimes, servers, and CRDS are installed in the namespace
seldon-mesh
:The output should be similar to this:
Note: Pods with names starting with seldon-dataflow-engine
, seldon-pipelinegateway
, and seldon-modelgateway
may generate log errors until they successfully connect to Kafka. This occurs because Kafka is not yet fully integrated with Seldon Core 2.
Next steps
You can integrate Seldon Core 2 with Kafka that is self-hosted or a managed Kafka.
Additional Resources
Last updated
Was this helpful?