Deploying the Industrial Edge Pattern

Prerequisites

1. An OpenShift cluster (Go to the OpenShift console). Cluster must have a dynamic StorageClass to provision PersistentVolumes. See also sizing your cluster.
2. (Optional) A second OpenShift cluster for edge/factory

The use of this pattern depends on having at least one running Red Hat OpenShift cluster. It is desirable to have a cluster for deploying the data center assets and a separate cluster(s) for the factory assets.

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.

Prerequisites

For installation tooling dependencies, see Patterns quick start

The Industrial Edge pattern installs an in-cluster gitea instance by default. This means that there is no need to fork the pattern’s git repository and that ArgoCD will point directly at the in-cluster git repository. Changes should be done there and not on github. See this post for more information.

How to deploy

1. Clone the industrial-edge repository on GitHub.

2. On your laptop or bastion host login to your cluster by using the oc login command or by exporting the KUBECONFIG file.

   oc login
   

   or

   export KUBECONFIG=~/my-ocp-cluster/auth/kubeconfig
   

3. Deploy the industrial edge pattern:

   cd <path-to-cloned-github-repository>
   ./pattern.sh make install
   

The make install target deploys the Validated Patterns Operator, all the resources that are defined in the values-datacenter.yaml

Validating the Environment

1. Verify that the following Operators are installed on the HUB cluster:

   $ oc get operators.operators.coreos.com -A
   NAME                                                  AGE
   advanced-cluster-management.open-cluster-management   3h8m
   amq-broker-rhel8.manuela-tst-all                      3h8m
   amq-streams.manuela-data-lake                         3h8m
   amq-streams.manuela-tst-all                           3h8m
   camel-k.manuela-data-lake                             3h8m
   camel-k.manuela-tst-all                               3h8m
   mcg-operator.openshift-storage                        3h7m
   multicluster-engine.multicluster-engine               3h4m
   ocs-client-operator.openshift-storage                 3h7m
   ocs-operator.openshift-storage                        3h7m
   odf-csi-addons-operator.openshift-storage             3h7m
   odf-operator.openshift-storage                        3h8m
   odf-prometheus-operator.openshift-storage             3h7m
   openshift-gitops-operator.openshift-operators         3h11m
   openshift-pipelines-operator-rh.openshift-operators   3h8m
   patterns-operator.openshift-operators                 3h12m
   recipe.openshift-storage                              3h7m
   rhods-operator.redhat-ods-operator                    3h8m
   rook-ceph-operator.openshift-storage                  3h7m
   

   Note: The list above was taken on OpenShift 4.16. It might change slightly depending on the OpenShift version being used (e.g. odf has less operator components on OpenShift 4.15 and earlier)

2. Access the ArgoCD environment

   You can find the ArgoCD application links listed under the nine box Red Hat applications in the OpenShift Container Platform web console.

   

   The most important ArgoCD instance to examine at this point is the Datacenter ArgoCD. This is where all the applications for the datacenter, including the test environment, can be tracked.

3. Check that all applications are synchronised. It should look like the following:

   

Next Steps

Once the data center has been setup correctly and confirmed to be working, you can:

1. Add a dedicated cluster to the main datacenter hub cluster.

   By default the factory applications defined in the values-factory.yaml file are deployed on all clusters imported into ACM and that have the label clusterGroup=factory

   For instructions on how to prepare and import a factory cluster please read the section importing a cluster. Use clusterGroup=factory as the label.

2. Once the data center and the factory have been deployed you will want to check out and test the Industrial Edge 2.0 demo code. You can find that here. The argo applications on the factory cluster will look like the following:

   

Uninstalling

We currently do not support uninstalling this pattern.

Help & Feedback

Help & Feedback - Report Bugs