[No AuthN/AuthZ] Deployment Using Feature Store Operator#

The Feature Store marketplace operator uses your current infrastructure to set up a Feature Store. It helps in setting up the Feature Store API server in your exisiting OKE cluster and MySQL database.

_images/oke.png

Installing the Feature Store Marketplace Operator#

The Feature Store Marketplace Operator can be installed from PyPi using the following command.

python3 -m pip install "oracle-ads[feature-store-marketplace]"

After that, the Operator is ready to go!

Configuration#

After having set up ads opctl on your desired machine using ads opctl configure, you are ready to begin setting up Feature Store. At a minimum, you need to provide the following details about your infrastructure:

  • The path to the OCIR repository where Feature Store container images are cloned.

  • The compartment ID where Feature Store is set up.

  • Database configuration details

  • The app name to use for Helm.

  • The namespace to use in the Kubernetes cluster.

  • The version of the Feature Store stack to install.

Optionally you can specify details for the API Gateway setup for Feature Store to enable authentication and authorization via OCI IAM:

  • Tenancy OCID

  • Region of deployment

  • User group OCIDs authorized to use Feature Store

  • OCID of resource manager stack to use for API Gateway deployment

These details can be easily configured in an interactive manner by running the command

ads operator init --type feature_store_marketplace

Prerequisites for running the operator#

Before running the operator you need to configure the following requirements:

  1. Helm: Helm is required to be installed on the machine for deploying Feature Store helm chart to the Kubernetes cluster. Ref: Installing Helm

  2. Kubectl: Kubectl is required to be installed to deploy the helm chart to the cluster. Ref: Installing Kubectl

  3. Policies: Required policies for API server and user running the operator.

  4. Setup cluster access locally

Run#

After the feature_store_marketplace.yaml is written using the init step above, you can start the deployment using:

Important

The installation will happen by default in default namespace. Ensure that NLB (Network Load Balancer) limit does not exceed the maximum limit.

ads operator run -f feature_store_marketplace.yaml -b marketplace

AuthN/AuthZ Setup (Optional)#

Users can also setup Feature Store API Gateway stack to enable authentication and authorization for Feature Store. This will allow us to access the feature store securely from a public endpoint using OCI IAM.