Skip to content

Update EKS values file used in setup #1685

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mrjones-plip merged 1 commit into from
Nov 7, 2024
Merged

Update EKS values file used in setup #1685

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 8 additions & 13 deletions content/en/contribute/medic/product-development-process/deploy-on-eks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,24 +85,19 @@ After you have created a ticket per "Request permission" above, you should get a
```

If get an error `no context exists with the name`, change `use-context` to `set-context` in the command. This will create the entry the first time. Subsequent calls should use `use-context`.
3. Create a new `values.yaml` file by [copying this one](https://github.com/medic/medic-infrastructure/blob/master/terraform/aws/dev/cht-projects/alpha-dev-cht-deploy-values.yaml). Be sure to update these values after you create it:
3. Create a new `values.yaml` file by [copying this one](https://github.com/medic/helm-charts/blob/main/charts/cht-chart-4x/values.yaml). Be sure to update these values after you create it:

{{< tabpane text=true >}}
{{% tab header="Single node CouchDB" %}}
* `alpha-dev` values to `USERNAME-dev`
* Update `certificate` to the latest value from SRE - currently it's `arn:aws:iam::720541322708:server-certificate/2024-wildcard-dev-medicmobile-org-chain`
* Add a strong `password` - this instance is exposed to the Internet! \*
* Put a UUID in `secret` - the command `uuidgen` is great for this
* Update `host` to be your `username`. For example: `mrjones.dev.medicmobile.org`
* `<your-project-name>` and `<your-namespace>` - set both `USERNAME-dev` - for example `mrjones-dev`
* `<password-value>` - put in a strong - this instance is exposed to the Internet! \*
* `<subdomain>` - your `username`. For example: `mrjones.dev.medicmobile.org`
{{% /tab %}}
{{% tab header="Multi node CouchDB" %}}
* `alpha-dev` values to `USERNAME-dev`
* Update `certificate` to the latest value from SRE - currently it's `arn:aws:iam::720541322708:server-certificate/2024-wildcard-dev-medicmobile-org-chain`
* Add a strong `password` - this instance is exposed to the Internet! \*
* Put a UUID in `secret` - the command `uuidgen` is great for this
* Update `host` to be your `username`. For example: `mrjones.dev.medicmobile.org`
* Set `noOfCouchDBNodes` to `3`
* Change `clusteredCouch_enabled` to be `true`
* `<your-project-name>` and `<your-namespace>` - set both `USERNAME-dev` - for example `mrjones-dev`
* `<password-value>` - put in a strong - this instance is exposed to the Internet! \*
* `<subdomain>` - your `username`. For example: `mrjones.dev.medicmobile.org`
* `clusteredCouch_enabled` - set to `true`
{{% /tab %}}
{{< /tabpane >}}

Expand Down