Skip to content
Permalink
Branch: master
Find file Copy path
2 contributors

Users who have contributed to this file

@cliveseldon @jklaise
93 lines (73 sloc) 4.07 KB

Install Seldon-Core

To install seldon-core on a Kubernetes cluster you have several choices:

  • If you have a Google Cloud Platform account you can install via the GCP Marketplace.

For CLI installs:

  • Decide on which package manager to use, we support:
    • Helm
    • Ksonnet
  • Decide on how you wish APIs to be exposed, we support:
    • Ambassador reverse proxy
    • Seldon's built-in OAuth API Gateway
  • Decide on whether you wish to contribute anonymous usage metrics. We encourage you to allow anonymous usage metrics to help us improve the project by understanding the deployment environments. More details can be found here
  • Does your Kubernetes cluster have RBAC enabled?
    • If not then disable Seldon RBAC setup

Follow one of the methods below:

With Helm

  • Install Helm
  • Install Seldon CRD. Set:
    • usage_metrics.enabled as appropriate.
helm install seldon-core-crd --name seldon-core-crd --repo https://storage.googleapis.com/seldon-charts \
     --set usage_metrics.enabled=true
  • Install seldon-core components. Set
    • apife.enabled : (default true) set to false if you have installed Ambassador.
    • rbac.enabled : (default true) set to false if running an old Kubernetes cluster without RBAC.
    • ambassador.enabled : (default false) set to true if you want to run with an Ambassador reverse proxy.
    • single_namespace : (default true) if set to true then Seldon Core's permissions are restricted to the single namespace it is created within. If set to false then RBAC cluster roles will be created to allow a single Seldon Core installation to control all namespaces. The installer must have permissions to create the appropriate RBAC roles. (>=0.2.5)
helm install seldon-core --name seldon-core --repo https://storage.googleapis.com/seldon-charts \
     --set apife.enabled=<true|false> \
     --set rbac.enabled=<true|false> \
     --set ambassador.enabled=<true|false>
     --set single_namespace=<true|false>

Notes

  • You can use --namespace to install seldon-core to a particular namespace
  • For full configuration options see here

With Ksonnet

ks init my-ml-deployment --api-spec=version:v1.8.0
  • Install seldon-core. Set:
    • withApife set to false if you are using Ambassador
    • withAmbassador set to true if you want to use Ambassador reverse proxy
    • withRbac set to true if your cluster has RBAC enabled
    • singleNamespace (default true) if set to true then Seldon Core's permissions are restricted to the single namespace it is created within. If set to false then RBAC cluster roles will be created to allow a single Seldon Core installation to control all namespaces. The installer must have permissions to create the appropriate RBAC roles. (>=0.2.5)
cd my-ml-deployment && \
    ks registry add seldon-core github.com/SeldonIO/seldon-core/tree/master/seldon-core && \
    ks pkg install seldon-core/seldon-core@master && \
    ks generate seldon-core seldon-core \
       --withApife=<true|false> \
       --withAmbassador=<true|false> \
       --withRbac=<true|false> \
       --singleNamespace=<true|false>
  • Launch components onto cluster
ks apply default

Notes

  • You can use --namespace to install seldon-core to a particular namespace

Other Options

Install with Kubeflow

Next Steps

You can’t perform that action at this time.