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.

Sign up for GitHub

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

Jump to bottom

[FEATURE] Add dynamic ingress-proxy TCP listener configuration #6

Open
xyzroller opened this issue May 14, 2022 · 1 comment
Open

[FEATURE] Add dynamic ingress-proxy TCP listener configuration #6

xyzroller opened this issue May 14, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@xyzroller
Copy link
Member

Feature request

Feature

Currently, TCP listeners on the ingress-proxy module have no effect, since there is no LXD proxy device added dynamically at project deploy-time. This means that containers requiring non-HTTP/S ports (e.g. Gitea) must be launched with static IP addresses and their own proxy devices.

Purpose of the feature

Solving this would allow project containers to be generally launched with dynamic IP addresses, simplifying configuration.

Additional information

Some way needs to be found for proxy devices to be added to the already-running ingress-proxy container during project deployment.
@xyzroller xyzroller added the enhancement New feature or request label May 14, 2022
@xyzroller
Copy link
Member Author

Cross links to primary repository and Codeberg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
1 participant
@xyzroller