You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, wou will need a cluster set up to deploy the eoAPI helm chart. This can be on AWS, GCP, or any other cloud provider that supports k8s. You can also run a local cluster using minikube.
35
+
36
+
### Local
37
+
38
+
For a local installation you can use:
39
+
40
+
*[Minikube](https://minikube.sigs.k8s.io/)
41
+
42
+
And simply execute the following commands:
43
+
44
+
```bash
45
+
$ make minikube
46
+
```
47
+
48
+
### Cloud
49
+
29
50
If you don't have a k8s cluster set up on AWS or GCP then follow an IaC guide below that is relevant to you
30
51
31
52
> ⓘ The helm chart in this repo assumes your cluster has a few third-party add-ons and controllers installed. So
32
53
> it's in your best interest to read through the IaC guides to understand what those defaults are
33
54
34
55
*[AWS EKS Cluster Setup](./docs/aws-eks.md)
35
-
36
56
*[GCP GKE Cluster Setup](./docs/gcp-gke.md)
37
-
57
+
58
+
Then simply execute the following command:
59
+
60
+
```bash
61
+
$ make deploy
62
+
```
63
+
38
64
<aname="helminstall"/>
39
65
40
-
## Helm Installation
66
+
## Manual helm installation
41
67
42
-
Once you have a k8s cluster set up you can `helm install` eoAPI with the following steps:
68
+
Instead of using the `make` commands above you can also manually`helm install` eoAPI with the following steps:
43
69
44
70
0.`eoapi-k8s` depends on the [Crunchydata Postgresql Operator](https://access.crunchydata.com/documentation/postgres-operator/latest/installation/helm). Install that first:
0 commit comments