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

Support SRV records for ClusterIP services #3993

Open
kwohlfahrt opened this issue Oct 16, 2023 · 7 comments · May be fixed by #4055
Open

Support SRV records for ClusterIP services #3993

kwohlfahrt opened this issue Oct 16, 2023 · 7 comments · May be fixed by #4055
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@kwohlfahrt
Copy link

kwohlfahrt commented Oct 16, 2023 •
edited

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.
@kwohlfahrt kwohlfahrt added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 16, 2023
@ghost
Copy link

ghost commented Nov 7, 2023

/assign
if this issue is available for work on, I am interested to work on this.
First time contributor, will try my best!!

@k8s-ci-robot k8s-ci-robot assigned ghost Nov 7, 2023
@melnikovx
Copy link

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.

@theloneexplorerquest theloneexplorerquest linked a pull request Nov 19, 2023 that will close this issue
Open
2 tasks
@theloneexplorerquest
Copy link
Contributor

@kwohlfahrt any change you can propose a use case? I created a PR and the reviewer was asking for valid use case 😊

@joryirving
Copy link

Any movement on this?

@k8s-triage-robot
Copy link

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 24, 2024
@k8s-triage-robot
Copy link

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 24, 2024
@joryirving
Copy link

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: SRV record on headless service theloneexplorerquest/external-dns
6 participants
@kwohlfahrt @k8s-ci-robot @joryirving @k8s-triage-robot @melnikovx @theloneexplorerquest