external-dns
external-dns copied to clipboard
Support SRV records for ClusterIP services
What would you like to be added:
Currently, there is support for generating SRV records from the ports of a NodePort service. There is also support for generating A/AAAA records that resolve to the IP address of headless services.
I would like to have support for generating the SRV records for headless services as well.
EDIT: And why not LoadBalancer as well, though I have no immediate use for this.
Why is this needed:
I already use the feature of generating A records for IP addresses of pods (using the AWS VPC CNI to allocate routeable addresses). I would also like to have service discovery based on SRV records for these same addresses.
/assign if this issue is available for work on, I am interested to work on this. First time contributor, will try my best!!
Hi, I would love to have SRV record support for LoadBalancer service type. The use case I have is to simulate Atlas mongoDB connector that uses SRV.
@kwohlfahrt any change you can propose a use case? I created a PR and the reviewer was asking for valid use case :blush:
Any movement on this?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale