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
This is due to the -dev-dir (cs3org/reva#416) picking all the files mounted from the ConfigMap and the pod's network space being shared. I'll fix it by creating a second ConfigMap for the gateway and its cfg. files.
In a production-ready future, we shall not run multiple revad goroutines in just one container but rather have one container per config file (+ its additional json files).
SamuAlfageme
added a commit
to SamuAlfageme/cs3orgcharts
that referenced
this issue
Jun 5, 2020
This will also allow in the future to ditch running
the main 'revad' container with -dev-dir by mounting
their config (.toml, .json, ...) on the righ container
Fix: cs3org#3
This will also allow in the future to ditch running
the main 'revad' container with -dev-dir by mounting
their config (.toml, .json, ...) on the righ container
Fix: cs3org#3
Won't reproduce again as we changed the pod layout after cs3org/reva#826 and removed the workDir and args parameters from the chart values to prevent using -dev-dir inside the pod in #7.
There is a collision of used ports as both reva and gateway containers use
the same gateway.toml
Related: #2
The text was updated successfully, but these errors were encountered: