git clone git@github.com:<your-username>/mlops-fraud-detection.gitDeploying the MLOps Fraud Detection pattern
Prerequisites
An OpenShift cluster (Go to the OpenShift console). Cluster must have a dynamic StorageClass to provision PersistentVolumes.
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.
The use of this pattern depends on having a Red Hat OpenShift cluster. In this version of the validated pattern there is no dedicated Hub / Edge cluster for the MLOps Fraud Detection pattern. This single node pattern can be extend as a managed cluster(s) to a central hub.
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.
Utilities
A number of utilities have been built by the validated patterns team to lower the barrier to entry for using the community or Red Hat Validated Patterns. To use these utilities you will need to export some environment variables for your cloud provider:
Preparation
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.
Clone the forked copy of this repository.
Create a local copy of the Helm secrets values file that can safely include credentials
DO NOT COMMIT THIS FILE
You do not want to push credentials to GitHub.
cp values-secret-mlops-fraud-detection.yaml.template ~/values-secret.yaml vi ~/values-secret.yaml
values-secret.yaml example
secrets:
//Nothing at time of writing.When you edit the file you can make changes to the various DB and Grafana passwords if you wish.
Customize the
values-global.yamlfor your deploymentgit checkout -b my-branch vi values-global.yaml
Replace instances of PROVIDE_ with your specific configuration
global:
pattern: mlops-fraud-detection
hubClusterDomain: "AUTO" # this is for test only This value is automatically fetched when Invoking against a cluster
options:
useCSV: false
syncPolicy: Automatic
installPlanApproval: Automatic
main:
clusterGroupName: hub git add values-global.yaml
git commit values-global.yaml
git push origin my-branchYou can deploy the pattern using the validated pattern operator. If you do use the operator then skip to Validating the Environment below.
Preview the changes that will be made to the Helm charts.
./pattern.sh make showLogin to your cluster using oc login or exporting the KUBECONFIG
oc loginor set KUBECONFIG to the path to yourkubeconfigfile. For exampleexport KUBECONFIG=~/my-ocp-env/auth/kubeconfig
Check the values files before deployment
You can run a check before deployment to make sure that you have the required variables to deploy the MLOps Fraud Detection Validated Pattern.
You can run make predeploy to check your values. This will allow you to review your values and changed them in
the case there are typos or old values. The values files that should be reviewed prior to deploying the
MLOps Fraud Detection Validated Pattern are:
| Values File | Description |
|---|---|
values-secret.yaml / values-secret-mlops-fraud-detection.yaml | This is the values file that will include the rhpam and fhir-psql-db sections with all database et al secrets |
values-global.yaml | File that is used to contain all the global values used by Helm |
Deploy
Apply the changes to your cluster
./pattern.sh make installIf the install fails and you go back over the instructions and see what was missed and change it, then run
make updateto continue the installation.This takes some time. Especially for the OpenShift Data Foundation operator components to install and synchronize. The
make installprovides some progress updates during the install. It can take up to twenty minutes. Compare yourmake installrun progress with the following video showing a successful install.Check that the operators have been installed in the UI.
To verify, in the OpenShift Container Platform web console, navigate to Operators → Installed Operators page.
Check that the Operator is installed in the
openshift-operatorsnamespace and its status isSucceeded.
Using OpenShift GitOps to check on Application progress
You can also check on the progress using OpenShift GitOps to check on the various applications deployed.
Obtain the ArgoCD URLs and passwords.
The URLs and login credentials for ArgoCD change depending on the pattern name and the site names they control. Follow the instructions below to find them, however you choose to deploy the pattern.
Display the fully qualified domain names, and matching login credentials, for all ArgoCD instances:
ARGO_CMD=`oc get secrets -A -o jsonpath='{range .items[*]}{"oc get -n "}{.metadata.namespace}{" routes; oc -n "}{.metadata.namespace}{" extract secrets/"}{.metadata.name}{" --to=-\\n"}{end}' | grep gitops-cluster` CMD=`echo $ARGO_CMD | sed 's|- oc|-;oc|g'` eval $CMDThe result should look something like:
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD hub-gitops-server hub-gitops-server-mlops-fraud-detection-hub.apps.mfd-cluster.aws.validatedpatterns.com hub-gitops-server https passthrough/Redirect None # admin.password xsyYU6eSWtwniEk1X3jL0c2TGfQgVpDH NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD cluster cluster-openshift-gitops.apps.mfd-cluster.aws.validatedpatterns.com cluster 8080 reencrypt/Allow None kam kam-openshift-gitops.apps.mfd-cluster.aws.validatedpatterns.com kam 8443 passthrough/None None openshift-gitops-server openshift-gitops-server-openshift-gitops.apps.mfd-cluster.aws.validatedpatterns.com openshift-gitops-server https passthrough/Redirect None # admin.password FdGgWHsBYkeqOczE3PuRpU1jLn7C2fD6The most important ArgoCD instance to examine at this point is
mlops-fraud-detection-hub. This is where all the applications for the pattern can be tracked.Check all applications are synchronised. There are thirteen different ArgoCD "applications" deployed as part of this pattern.
Next Steps
