...
There are two methods for fetching the Helm Charts from ModelOp, either by requesting a tar.gz compressed file of the content of the Git repository where the Helm Charts reside from your ModelOp Account Executive or Sales Engineer, which will be delivered via bucket link.
...
Within the "installer" directory, the installer/generatePullSecrets.sh script is used to generate secrets within Kubernetes in order to allow the cluster to import images.
The installerscss/3.0-sccs-compat.application.yaml file contains certain default settings for a ModelOp Center v.3.0 installation which include SCCS (Spring Cloud Configuration Server) which is used as the backing configuration service for ModelOp services.
...
Chart.yaml contains a description of the chart, it is a place to track details on what is deployed.
The my-config installer/moc/sccs directory contains all of the base yaml files that will be used by Spring Cloud Configuration Server to configure the ModelOp Center application.
...
helm install RELEASENAME DIRECTORY --set moc.version=DESIREDVERSION --namespace TARGETNAMESPACE -f 3.0-sccs-compat.DIRECTORY/scss/application.yaml
Whereby:
RELEASENAME = The name given to the release, tracked by Helm, which can be anything relevant to the deployment itself. e.g. "moc-dev-helm1" Please see the following documentation that describes the concept of a Helm Release: https://helm.sh/docs/intro/using_helm/#three-big-concepts
...
helm install moc-test-rel1 moc-test --set moc.version=3.0 --namespace moc-test-1 -f 3.0-sccs-compatDIRECTORY/scss/application.yaml
This example command assumes the existence of the directory %helm-installer/installer/moc-test which is a copy of the %helm-installer/installer/moc directory with all values changed to what is desired for the environment.
...