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
Copy file name to clipboardExpand all lines: README.md
+93-9Lines changed: 93 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -112,7 +112,7 @@ You need to clone the [opencrvs-core](https://github.com/opencrvs/opencrvs-core)
112
112
```
113
113
6. [Temporary Step] Switch to the k8s-version branch:
114
114
```bash
115
-
git checkout k8s-version
115
+
git checkout k8s-refresh
116
116
```
117
117
7. Run Tilt:
118
118
```bash
@@ -123,27 +123,55 @@ You need to clone the [opencrvs-core](https://github.com/opencrvs/opencrvs-core)
123
123
124
124
---
125
125
126
-
## [🚧 Coming soon] For OpenCRVS Country Configuration Developers
126
+
## For OpenCRVS Country Config Developers
127
127
128
-
You need to fork the [opencrvs-countryconfig](https://github.com/opencrvs/opencrvs-countryconfig) repository and clone the [infrastructure](https://github.com/opencrvs/infrastructure) repository. If these repositories are already on your laptop, ensure they are in the same folder.
128
+
Please follow official documentation how to setup your own country configuration at [Set-up your own, local, country configuration](https://documentation.opencrvs.org/setup/3.-installation/3.2-set-up-your-own-country-configuration).
129
+
You need to fork (clone) the [opencrvs-countryconfig](https://github.com/opencrvs/opencrvs-countryconfig) repository and clone the [infrastructure](https://github.com/opencrvs/infrastructure) repository. If repositories are already on your laptop, ensure they are in the same parent folder, for example:
130
+
```
131
+
repositories/
132
+
infrastructure
133
+
opencrvs-countryconfig
134
+
...
135
+
```
129
136
130
-
1. Create a new folder or use an existing folder to store the repositories.
137
+
**Step by step instruction**
138
+
139
+
1. Create a new folder or use an existing folder to store the repositories. For example folder could be located at your home directory or in documents:
140
+
```bash
141
+
mkdir ~/Documents/repository
142
+
```
131
143
2. Open a terminal (command line) and navigate to the folder.
132
-
3. Clone your fork of the OpenCRVS Country Configuration repository:
<td>Elasticsearch configuration, including the hostname and port. TODO: Consider defining the port as a separate variable.</td>
21
+
<td>Elasticsearch configuration, including the hostname and port.<br> <b>NOTE</b>: Some services require authentication, please use secrets to redefine ES_HOST variable if needed.</td>
22
22
</tr>
23
23
<tr>
24
24
<td>influxdb.host</td>
@@ -55,6 +55,11 @@ Helm chart to deploy all OpenCRVS services on Kubernetes cluster.
@@ -80,26 +85,17 @@ Helm chart to deploy all OpenCRVS services on Kubernetes cluster.
80
85
<td>{}</td>
81
86
<td>Mapping kubernetes secrets as environment variables. For more information see [Mapping secrets](#mapping-secrets)</td>
82
87
</tr>
88
+
<tr>
89
+
<td>data_seeder.enabled</td>
90
+
<td>true</td>
91
+
<td>Seed data as post-install step, data seeder is executed only once while `helm install`. In some cases when data is already seeded, e/g upgrade, this value must be set to false. **Note**: default user is used for data seeding, it will fail anyway on database with non-default data.</td>
Helm chart allows to define environment variables in following scopes:
91
-
-**Global variables** are defined at top level of values file and is added to all containers. See `env` key in [values.yaml](values.yaml)
92
-
-**Service level variables** are defined for each particular service. See `<service_name>.env` key in [values.yaml](values.yaml)
93
-
-**Secret environment variables** are defined at service level as `<service_name>.secrets` key, see [values.yaml](values.yaml).
94
96
95
97
# Mapping secrets
96
98
97
-
Suppose we need to store ES_HOST variable as a secret since it contains url with login and password for Elastic search.
98
-
Kubernetes secret is key/value object usually created from `.env` file, for example:
99
-
```
100
-
ES_HOST=user:randompass@elasticsearch:9200
101
-
```
102
-
103
99
Mapping needs to be added for particular service to access variable inside workload (service), e/g for `search` service to access ES_HOST following configuration is needed:
104
100
```
105
101
search:
@@ -117,4 +113,37 @@ secrets:
117
113
Summary:
118
114
-`secret_name`, name of Kubernetes secret object
119
115
-`secret_key`, key (variable name) inside Kubernetes secret data property
120
-
-`environment_variable`, environment variable name inside container. If `secret_key` value `environment_variable` are the same, last one can be omitted.
116
+
-`environment_variable`, environment variable name inside container. If `secret_key` value `environment_variable` are the same, last one can be omitted.
117
+
118
+
**Step by step example**
119
+
120
+
Suppose we need to store ES_HOST variable as a secret and provide variable value to service `search`.
0 commit comments