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.

...

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 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"

Windows

It is strongly recommended that the aforementioned commands be run using WSL: https://learn.microsoft.com/en-us/windows/wsl/about

Useful Links

Kubernetes Installation Documentation:
https://kubernetes.io/docs/setup/
Kubectl Installation Documentation:
https://kubernetes.io/docs/tasks/tools/
Creating a kube-config Context using kubectl:
https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/
Helm Installation Documentation:
https://helm.sh/docs/intro/install/
ModelOp DockerHub Repository:
https://hub.docker.com/u/modelop

...

moc/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/ . Again, it is not recommended that the values.yaml file be modified. Rather, the simple.yaml file should be filled out with whatever values you wish to override.

...

moc:
  namespace: my-moc-namespace
  version: "3.1"

Assuming the Then trigger the installation by running the following command from the directory that contains the moc directory:

...

To fetch the IP of the ModelOp Gateway pod, simply ensure you are in the targeted namespace chosen for deployment, and use the following command:

`$$ kkubectl get services | grep gateway`gateway

Output should resemble the following as an example:

$ kkubectl get services | grep gateway
gateway               LoadBalancer   10.100.8.109     abb3888bb91fc49d5a101f1a1340d5b8-116610426.us-east-2.elb.amazonaws.com   8090:30285/TCP   70d

...