-
Notifications
You must be signed in to change notification settings - Fork 2
/
instructions.txt
50 lines (30 loc) · 1.65 KB
/
instructions.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
# OpsMx Secure Software Delivery
For more information, visit https://www.opsmx.com
## Spinnaker + OpsMx Secure Software Delivery (SSD) Setup Instructions
### Prerequisites
- Kubernetes cluster 1.19 or later with at least 6 cores and 20 GB memory
- Helm 3 is setup on the client system
```console
$ helm version
```
If helm is not setup, follow <https://helm.sh/docs/intro/install/> to install helm.
```console
$ kubectl create namespace opsmx-ssd
```
1. Clone the enterprise-ssd
```console
git clone https://github.com/OpsMx/enterprise-ssd
```
## Specify inputs based on your environment and git-repo
*The installation process requires inputs such as the application version, git-repo details and so on.*
2. **Update rcimages-values.yaml as required**, specifically: At at **minimum** the SSD URL and gitops-repo details in spinnaker.gitopsHalyard section must be updated. Please read the inline comments in rcimages-values.yaml and update accordinlgy
## Start the installation
*The installation is done through helm.*
3. Install SSD by executing this command:
`helm install ssd charts/ssd -f rcimages-values.yaml -n opsmx-ssd --timeout=20m`
## Monitor the installation process
4. Wait for all pods to stabilize (about 10-20 min, depending on your cluster load). The "oes-config" in Completed status indicates completion of the installation process. Check status using:
- `kubectl -n opsmx-ssd get po -w`
## Check the installation
5. Access SSD using the URL specified in the values.yaml in step 5 in a browser such as Chrome.
6. Login to the SSD instance with user/password as admin and opsmxadmin123, if using the defaults for build-in LDAP.