Headless service: allow to specify target as NodeExternalIP or by annotation

[alfredkrohmer]

Description

If external-dns.alpha.kubernetes.io/target annotation is present on a
pod, it's value will be used as the target for the headless service.

If annotation external-dns.alpha.kubernetes.io/access=public is present,
NodeExternalIP of the node running the pod is used as the target for the
headless service.

Checklist

• Unit tests updated
• End user documentation updated

[seanmalloy]

/kind feature

[benesch]

This would be super useful to us at @MaterializeInc! Any chance this could be reviewed and merged?

[alex-hunt-materialize]

Any update on this? We've been using a fork with this change and it's been working great.
https://github.com/MaterializeInc/external-dns

[robert-heinzmann-logmein]

Any updates on this PR ?

[k8s-triage-robot]

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

[alex-hunt-materialize]

/remove-lifecycle stale

Any update on this? It works great for us. We'd really like to point back at the upstream.

[alex-hunt-materialize]

Bump. We've had no issues with our fork containing this PR after running it in production for months. We'd really love to point back at upstream, but we can't until this is merged.

[alex-hunt-materialize]

Bump. We'd love to get this merged so we can stop using a fork.

[Raffo]

/check-cla

[Raffo]

@alfredkrohmer you need to merge master in your branch to make sure the build passes.

[alfredkrohmer]

@Raffo rebased from master

[Raffo]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alfredkrohmer, Raffo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Raffo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment