meissa/c4k-taiga
6
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity

Update readme

Browse source
This commit is contained in:
erik 2023-08-09 16:07:02 +02:00
parent e2d5fd6723
commit c34db7c400
1 changed files with 11 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
README.md
View file

@ -79,9 +79,18 @@ https://github.com/kaleidos-ventures/taiga-back/blob/main/settings/config.py.pro
* rabbit-mq * rabbit-mq
### Networking ### Networking
https://github.com/compose-spec/compose-spec/blob/master/spec.md
We need to know what the "hostname" KW does in docker compose.
Then need to find a translation for this functionality to kubernetes. The `hostname` KW sets the hostname of a container.
It should have no effect on the discoverability of the container in kubernetes.
The `networks` KW defines the networks that service containers are attached to, referencing entries under the top-level networks key.
This should be taken care of by our kubernetes installation.
Taiga containers that need to reach other taiga containers:
taiga-async -> taiga-async-rabbitmq
taiga-events -> taiga-events-rabbitmq
ToDo: How do we direct traffic towards the frontend pod? ToDo: How do we direct traffic towards the frontend pod?
Do we need to touch the frontend config regarding the default address (localhost:9000) of the API? Do we need to touch the frontend config regarding the default address (localhost:9000) of the API?