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

Connect to specific networks #3

Merged
merged 5 commits into from
May 1, 2024
Merged

Conversation

obeone
Copy link
Owner

@obeone obeone commented May 1, 2024

Add the ability to indicate which network to connect.

So if you have a container connected to a public and a db networks, you can limit traefik to connect to public

obeone added 5 commits May 1, 2024 07:37
- Added a new function to check if the Traefik container is running before network connection operations.
- Adjusted the connection logic to consider allowed networks specified in the container's labels and account for external networks.
- Improved logging and error handling for network connection and disconnection operations.
- Enhanced event monitoring to skip handling events if Traefik is not running.
Added a new service for Traefik with specific configurations and ports.
…bility to specify networks to connect to

Adjusts the configuration key `monitoredLabel` to `traefik.monitoredLabel` for consistency. Additionally, introduces the ability to specify networks for Traefik to connect to by setting the `autoproxy.networks` label on Docker containers. This enhancement provides more control over network connections managed by Traefik.
@obeone obeone merged commit 2280eb8 into main May 1, 2024
4 checks passed
@obeone obeone deleted the connect_to_specific_networks branch May 1, 2024 07:00
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.

1 participant