Skip to content
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.

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

Davrods: networking update to work with new iptables #662

Merged
merged 2 commits into from
Oct 25, 2022

Conversation

scimerman
Copy link
Contributor

Currently we have
:443 incoming packets at host > iptables (co-managed by docker) > docker software bridge > :443 instance

I eliminated the use of software bridge:

... which allows containers connected to the same bridge network to communicate, while providing isolation from containers which are not connected to that bridge network.

Since we do not intend to make more docker instances on irods production machines, where we would connect some, but isolate other instance, this option is removed.

I changed davrods to be working on host network instead:

... container’s network stack is not isolated from the Docker host (the container shares the host’s networking namespace), and the container does not get its own IP-address allocated.

This will change to:
incoming packets > iptables > exposed port at the docker instance

Tested on production machine: works


Also removed the entire filebeat dependency, as we do not use it and was even hard coded to internal Maastrichts url of control their online status machine.

@pneerincx pneerincx merged commit 26f4740 into rug-cit-hpc:develop Oct 25, 2022
@scimerman scimerman deleted the davrods branch November 18, 2022 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants