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: CHANGELOG.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
23
23
- Change above affects also `"response_from": "kafka"` proxy functionality. RIG will forward to clients only Kafka body, no headers. This means, when using binary mode, clients receive only the data part, no CloudEvents context attributes.
24
24
- Changed `response_from` handler to expect a message in binary format, **NOT** a cloud event (`kafka` and `http_async`). [#321](https://github.com/Accenture/reactive-interaction-gateway/pull/321)
25
25
- Updated Helm v2 template, kubectl yaml file and instructions in the `deployment` folder [#288](https://github.com/Accenture/reactive-interaction-gateway/issues/288)
26
+
- Publish Helm Chart to Github pages. With this change, we can simply install the chart using
Check out the [Helm v2 README](helm/reactive-interaction-gateway-helm-v2/README.md) or [Helm v3 README](./helm/reactive-interaction-gateway/README.md) and [Operator's Guide](https://accenture.github.io/reactive-interaction-gateway/docs/rig-ops-guide.html) for more information on configuring RIG.
10
14
11
-
The Helm Charts in [./helm/reactive-interaction-gateway-helm-v2](./helm/reactive-interaction-gateway-helm-v2) and [./helm/reactive-interaction-gateway](./helm/reactive-interaction-gateway) are essentially the same but only use a different `apiVersion` in the `Chart.yaml`.
15
+
## Deploy with kubectl
12
16
13
-
### Version 2
17
+
> This deployment is not recommended as lots of configurations is hard coded
You can also inspect the logs of the pods with `kubectl logs <pod_name>` to see how they automatically re-balance Kafka consumers (if you are using Kafka) and adapt Proxy APIs from other nodes.
58
53
59
-
## Configuration
54
+
###Configuration
60
55
61
-
### Node host
56
+
####Node host
62
57
63
58
Every node in cluster needs to be discoverable by other nodes. For that Elixir/Erlang uses so called `long name` or `short name`. We are using `long name` which is formed in the following way `app_name@node_host`. `app_name` is in our case set to `rig` and `node_host` is taken from environment variable `NODE_HOST`. This can be either IP or container alias or whatever that is routable in network by other nodes.
64
59
@@ -71,13 +66,13 @@ We are using the pod IP with:
71
66
fieldPath: status.podIP
72
67
```
73
68
74
-
### Node cookie
69
+
#### Node cookie
75
70
76
71
Nodes in Erlang cluster use cookies as a form of authorization/authentication between them. Only nodes with the same cookie can communicate together. Ideally, it is some generated hash, that's why we recommend adapting `NODE_COOKIE` environment variable in the `values.yaml`.
77
72
78
-
### Additional configuration
73
+
#### Additional configuration
79
74
80
-
You can configure bunch of environment variables, please check the [Operator's Guide](https://accenture.github.io/reactive-interaction-gateway/docs/rig-ops-guide.html).
75
+
You can configure bunch of environment variables, please check the [Helm v2 README](helm/reactive-interaction-gateway-helm-v2/README.md) or [Helm v3 README](./helm/reactive-interaction-gateway/README.md) and [Operator's Guide](https://accenture.github.io/reactive-interaction-gateway/docs/rig-ops-guide.html).
Copy file name to clipboardExpand all lines: docs/rig-dev-guide.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,7 @@ To have the project use a newer Elixir version, make sure to change the followin
44
44
45
45
- Increment `rig` version in the [version](../version) file
46
46
- Increment `appVersion` in the [Helm v2 Chart.yaml](../deployment/helm2/reactive-interaction-gateway/Chart.yaml) and [Helm v3 Chart.yaml](../deployment/helm3/reactive-interaction-gateway/Chart.yaml) files
47
+
- Update Helm chart README files: install [helm-docs](https://github.com/norwoodj/helm-docs) and run `helm-docs` in the root directory
47
48
- Increment image tag in the [Kubernetes rig.yaml](../deployment/kubectl/rig.yaml) file
48
49
- In [CHANGELOG.md](../CHANGELOG.md), rename `[Unreleased]` and add a corresponding link to the bottom of the file
49
50
- Create a signed Git tag either using `git -s` or by creating a release using the Github UI
0 commit comments