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

vmauth: support dns domain as route destination #5707

Closed
Haleygo opened this issue Jan 28, 2024 · 2 comments
Closed

vmauth: support dns domain as route destination #5707

Haleygo opened this issue Jan 28, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request vmauth

Comments

@Haleygo
Copy link
Collaborator

Haleygo commented Jan 28, 2024

Is your feature request related to a problem? Please describe

vmauth can balance load among multiple HTTP backends defined under url_prefix with different mode.
In Kubernetes, if users want to perform loadbalance on workload's pods, they need to list all the pods' subdomain[since address is normally changed after pod recreate] under url_prefix, and for now it's only possible for statefulset since they can have fixed subdomain.
But sometimes user can't give the entire server list or the server addresses can change dynamically, and this list is already maintained by other dns server. Like for deployment, we can also use a Headless Service to control the domain of pods.

Describe the solution you'd like

It will be great if we can config this domain in vmauth directly, and vmauth will periodically re‑resolve the domain names into IP addresses and load balancing across the set of addresses.

Describe alternatives you've considered

No response

Additional information

No response

@Haleygo Haleygo added enhancement New feature or request vmauth labels Jan 28, 2024
@Haleygo Haleygo self-assigned this Feb 1, 2024
valyala added a commit that referenced this issue Mar 6, 2024
…spreading load among the discovered ips

This is done with the `discover_backend_ips` option at `user` and `url_map` level.

Updates #5707
valyala added a commit that referenced this issue Mar 6, 2024
…spreading load among the discovered ips

This is done with the `discover_backend_ips` option at `user` and `url_map` level.

Updates #5707
@valyala
Copy link
Collaborator

valyala commented Mar 6, 2024

FYI, this functionality has been implemented in the commit 7b2b980 . See these docs for details. This commit will be included in the next release. In the mean time this functionality can be tested by building vmauth from the commit according to these docs.

hardproblems pushed a commit to hardproblems/VictoriaMetrics that referenced this issue Mar 13, 2024
…spreading load among the discovered ips

This is done with the `discover_backend_ips` option at `user` and `url_map` level.

Updates VictoriaMetrics#5707
possibull pushed a commit to possibull/VictoriaMetrics that referenced this issue Mar 27, 2024
…spreading load among the discovered ips

This is done with the `discover_backend_ips` option at `user` and `url_map` level.

Updates VictoriaMetrics#5707
possibull pushed a commit to possibull/VictoriaMetrics that referenced this issue Mar 27, 2024
…spreading load among the discovered ips

This is done with the `discover_backend_ips` option at `user` and `url_map` level.

Updates VictoriaMetrics#5707
@valyala
Copy link
Collaborator

valyala commented Apr 4, 2024

DNS-based discovering of backend IPs is available in vmauth starting from v1.100.0. See these docs for details.

Closing the feature request as done.

@valyala valyala closed this as completed Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request vmauth
Projects
None yet
Development

No branches or pull requests

2 participants