Page Comparison

...

As part of this walkthrough, it is important to note that the items chosen for deployment via Helm, can be added or removed as seen fit, given the chosen configuration of the environment. For instance, Spring Cloud Configuration Server, which is the backing configuration mechanism for ModelOp Center. If You can find additional information regarding advanced configurations in the "Additional Configuration" section of this documentation.

...

There are a few key items that will need to be available prior to deploying ModelOp Center. Firstly, a Kubernetes cluster that has access to either DockerHub via the web, or an image repository that has the ModelOp Center images stored. Second, a workstation or jumpbox/server that has a properly credentialled and configured kubectl cli utility which allows for interaction with the Kubernetes cluster. Thirdly, the Helm utility, version 3+, will be necessary for deployment. Kubectl will require a properly configured context will be necessary to connect to the Kubernetes cluster, which can be done using the kubectl utility itself. Lastly, the ModelOp Center images will be necessary for the deployment. The images can either be accessed directly from DockerHub, as well as from a repository of your choosing, which may be inside your network as well.

...

1. Ensure that a Kubernetes cluster has been allocated and is running, available, and usable with credentials that have adequate access. This will be likely managed by enterprise IT, whereby either an existing cluster or a new one is made available to use. Please ensure that this step is completed, though the following steps can be accomplished in parallel to having the Kubernetes cluster created/allocated. The link to installing Kubernetes has been provided below, though as mentioned, a specific enterprise team will likely create the cluster/infrastructure.

2. Ensure that the kubectl utility kubectl is installed and functional on the workstation or chosen jumpbox/server. Installation of the utility can be accomplished by following the guide here: https://kubernetes.io/docs/tasks/tools/

3. Ensure that a context is properly set so that connectivity can be established with your cluster following this guide: https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/

4. To ensure that kubectl is working correctly, the output of the following command should result in the displaying of the namespaces for the context in which you are operating: kubectl get namespaces Note that if this command is not generating output correctly, please invoke the assistance of your enterprise support teams to assist in the installation.

5. Ensure that Helm is installed and operational by following the guide found here: https://helm.sh/docs/intro/install/

6. To test that Helm is ready and available, please run: helm version which should generate output similar to: version.BuildInfo{Version:"v3.9.0", GitCommit:"7ceeda6c585217a19a1131663d8cd1f7d641b2a7", GitTreeState:"clean", GoVersion:"go1.18.2"}

7. Ensure that the version of Helm that is currently being used is 3.0+. e.g. Version:"v3.9.0"

...

Within the copied directory, there are a number of files that are created, but at the root of the environment directory there are two primary files:

values.yaml contains the bulk majority of the configurations that will need to be modified and made specific to the environment they are targeting. Please find information related to the values file here: https://helm.sh/docs/chart_best_practices/values/

Chart.yaml contains details about what will describe the release once installeda description of the chart, it is a place to track details on what is deployed.

...

Modifying the values.yaml file is necessary to tailor the installation to the targeted environment. The main section of values.yaml that should be modified is moc, which contains a number of key/values that need to be set to adjust the deployment to specific needs. Please refer both to the following documentation, with general guidelines on the sections, as well as the in-line comments that are part of the file itself.

...

The ModelOp Center Pre-Install utility represents is a utility that allows the user to ensure that all configurations resolve correctly prior to continuing with installation. Please refer to the following documentation before continuing: ModelOp Center Pre-Install Utility

...

Note the IP address and the port that is allocated by default. To connect to the newly instantiated deployment of ModelOp Center, access the landing page via:

<http://<IP><IP Address>:<Port>

Example using the above output:

...