[Feature Request] Support ClusterIP services with externalIPs set

ConnorJC3 commented 4 years ago

It is possible to specify the externalIPs manually on a ClusterIP service, which causes kube-proxy to bind to those ports on any node with that IP on one of its network interfaces and forward traffic into the cluster. Minimal example service:

apiVersion: v1
type: Service
metadata:
  name: example
  annotations:
    external-dns.alpha.kubernetes.io/hostname: example.com
spec:
  type: ClusterIP
  selector:
    app: example
  ports:
  - name: example-http
    port: 80
    targetPort: 80
  externalIPs:
  - aaa.bbb.ccc.ddd

As of right now kube-external-dns does not create an A record for services like this, it only does so for LoadBalancer services. It would be great if these services also could be managed via kube-external-dns (Note: I'm using a service like this because I require use of both TCP and UDP on the same port, which is not supported with LoadBalancer services at the moment).

altreze commented 4 years ago

@ConnorJC3 did you have any chance working on this feature ?

fejta-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

ConnorJC3 commented 4 years ago

/remove-lifecycle stale Still wanted and not in external-dns to my knowledge.

@altreze no, I did not

TimoKoole commented 4 years ago

I would also like this feature.

seanmalloy commented 4 years ago

/kind feature

fejta-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

seanmalloy commented 4 years ago

/remove-lifecycle stale

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

ConnorJC3 commented 3 years ago

Still wanted.

/remove-lifecycle stale

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

fejta-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten

fejta-bot commented 3 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

k8s-ci-robot commented 3 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/1281#issuecomment-879231879): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

briscula commented 3 years ago

+1

samcday commented 2 years ago

/reopen

samcday commented 2 years ago

/remove-lifecycle rotten

k8s-ci-robot commented 2 years ago

@samcday: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/1281#issuecomment-1010899231): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

ConnorJC3 commented 2 years ago

/reopen

k8s-ci-robot commented 2 years ago

@ConnorJC3: Reopened this issue.

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/1281#issuecomment-1015095279): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

darkedges commented 2 years ago

will try and work on this feature as I need it for an issue I am having. Trying to currently understand how the code works as there is currently code to do this, but for another service.

torbendury commented 2 years ago

@darkedges @ConnorJC3 did you manage to make any progress on this? We are currently building a setup with external-dns and just ran into this missing feature, which leads to external-dns creating DNS entries for ClusterIPs.

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

ConnorJC3 commented 2 years ago

/remove-lifecycle stale

k8s-triage-robot commented 2 years ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
Mark this issue or PR as rotten with /lifecycle rotten
Close this issue or PR with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

adampl commented 2 years ago

/remove-lifecycle stale

adampl commented 2 years ago

/lifecycle frozen

kinseii commented 1 year ago

I need this too

kubernetes-sigs / external-dns

[Feature Request] Support ClusterIP services with externalIPs set #1281