Validated Patterns

Deploying the MLOps Fraud Detection pattern

Prerequisites

  1. An OpenShift cluster (Go to the OpenShift console). Cluster must have a dynamic StorageClass to provision PersistentVolumes.

  2. A GitHub account (and a token for it with repositories permissions, to read from and write to your forks)

For installation tooling dependencies, see Patterns quick start.

If you do not have a running Red Hat OpenShift cluster you can start one on a public or private cloud by using Red Hat’s cloud service.

Installing this pattern

  1. Fork the mlops-fraud-detection repo on GitHub. It is necessary to fork because your fork will be updated as part of the GitOps and DevOps processes.

  2. Clone the forked copy of this repository.

    git clone git@github.com:<your-username>/mlops-fraud-detection.git

  3. Login to your cluster using oc login or exporting the KUBECONFIG

    oc login
    or set KUBECONFIG to the path to your kubeconfig file. For example
    export KUBECONFIG=~/my-ocp-env/auth/kubeconfig

  4. Install this pattern on your cluster

    ./pattern.sh make install

The installation will conclude when all the ArgoCD applications installed as part of this pattern are healthy and synced.

Next Steps

Edit this page Open a documentation issue

QUICKLINKS

CONTRIBUTE

STAY IN TOUCH

Validated Patterns

Validated Patterns are an evolution of how you deploy applications in a hybrid cloud. With a pattern, you can automatically deploy a full application stack through a GitOps-based framework. With this framework, you can create business-centric solutions while maintaining a level of Continuous Integration (CI) over your application.