Config Repository
The Config Repository represents the "source of truth" that (along with the Charts in the Source Repository and the secrets in the Secrets Vault) provides everything ArgoCD needs to install and manage MAS instances across Target Clusters.
It is structured as a hierarchy, with "accounts" at the top, followed by "clusters", followed by "instances". Each level contains different types of YAML configuration files. Each YAML configuration file will cause ArgoCD to generate one (or more) application(s), which in turn render Helm charts into the appropriate Target Cluster.
Here is the structure of an example Config Repository containing configuration for three accounts (dev
, staging
, production
) with a number of clusters and MAS instances:
├── dev
│ ├── cluster1
│ │ ├── instance1
│ │ │ └── *.yaml
│ │ ├── instance2
│ │ │ └── *.yaml
│ │ ├── instance3
│ │ │ └── *.yaml
│ │ └── *.yaml
│ └── cluster2
│ ├── *.yaml
│ └── instance1
│ └── *.yaml
├── staging
│ └── cluster1
│ ├── instance1
│ │ └── *.yaml
│ ├── instance2
│ │ └── *.yaml
│ └── *.yaml
└── production
└── cluster1
├── *.yaml
├── instance1
│ └── *.yaml
└── instance2
└── *.yaml
The current set of YAML configuration files recognised by MAS GitOps at each level is as follows:
├── <ACCOUNT_ID>
│ └── <CLUSTER_ID>
│ ├── <INSTANCE_ID>
│ │ ├── ibm-cp4d-services-base.yaml
│ │ ├── ibm-cp4d.yaml
│ │ ├── ibm-db2u.yaml
│ │ ├── ibm-db2u-databases.yaml
│ │ ├── ibm-mas-instance-base.yaml
│ │ ├── ibm-mas-masapp-assist-install.yaml
│ │ ├── ibm-mas-masapp-configs.yaml
│ │ ├── ibm-mas-masapp-predict-install.yaml
│ │ ├── ibm-mas-masapp-iot-install.yaml
│ │ ├── ibm-mas-masapp-manage-install.yaml
│ │ ├── ibm-mas-masapp-monitor-install.yaml
│ │ ├── ibm-mas-masapp-optimizer-install.yaml
│ │ ├── ibm-mas-masapp-visualinspection-install.yaml
│ │ ├── ibm-mas-suite-configs.yaml
│ │ ├── ibm-mas-suite.yaml
│ │ ├── ibm-mas-workspaces.yaml
│ │ ├── ibm-sls.yaml
│ │ ├── ibm-spss.yaml
│ │ └── ibm-wml.yaml
│ │ └── ibm-wsl.yaml
│ ├── ibm-dro.yaml
│ ├── ibm-mas-cluster-base.yaml
│ ├── ibm-operator-catalog.yaml
│ ├── nvidia-gpu-operator.yaml
│ └── redhat-cert-manager.yaml
Info
See example-config for examples of each of these YAML files for a single account, cluster and MAS instance.