Headless should use ExternalIP when using --publish-host-ip

[kevincox]

Right now when publishing a headless service it uses the internal IP which means that it can't receive inbound connections.

I think this should be the default since the service code prefers external IP. However it might be best to avoid changing current behaviour.

[iameli]

Just encountered this as well - the documentation seems to imply that it's designed for routing to nodes from the internet ("when trying to access them from outside the cluster") — perhaps there's a bug?

[iameli]

Got the behavior I wanted by using a service with type: NodePort and externalTrafficPolicy: Local. I'm not entirely sure why that particular code path has this behavior but the end result works well.

[fejta-bot]

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

[protometa]

I'm confused by this as well.

[fejta-bot]

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-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[kevincox]

/remove-lifecycle rotten

[mhoran]

#1391 should resolve this; it's working for my purposes. Both --publish-host-ip and an annotation (external-dns.alpha.kubernetes.io/use-external-host-ip) must be added for this to work as expected.

[fejta-bot]

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

[mhoran]

/remove-lifecycle stale

[seanmalloy]

/kind feature

[stefanlasiewski]

@iameli

Got the behavior I wanted by using a service with type: NodePort and externalTrafficPolicy: Local. I'm not entirely sure why that particular code path has this behavior but the end result works well.

Were you still using a Headless service to do this, or not?

[iameli]

@stefanlasiewski Here's the manifest:

apiVersion: v1
kind: Service
metadata:
  name: admin-marker
  labels:
    app: admin-marker
  annotations:
    livepeer.live/admin-external-dns: "true"
    external-dns.alpha.kubernetes.io/hostname: "[redacted]"
    external-dns.alpha.kubernetes.io/ttl: "120"
spec:
  type: NodePort
  externalTrafficPolicy: Local
  selector:
    app: admin-marker
  ports:
    - port: 443
      targetPort: 443
      protocol: TCP
      name: https

[stefanlasiewski]

Thanks @iameli. Looks like your solution was to use the NodePort service type, instead of a Headless service (probably due to this bug).

I have a similar NodePort service, and it's using the internal IP address of the node, not the external IP. I'm looking around for a solution.

[fejta-bot]

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

[unixfox]

/remove-lifecycle stale

[fejta-bot]

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

[unixfox]

/remove-lifecycle stale

[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

[mhoran]

/remove-lifecycle stale

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[unixfox]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active 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:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[kevincox]

"complete"

[kevincox]

/remove-lifecycle rotten

[kevincox]

/reopen

[k8s-ci-robot]

@kevincox: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[seh]

Does #2115 satisfy this desire? (Witness the similar #1077 as well.)

[kevincox]

Yes! Thanks for pointing that out. The final docs are here: https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/hostport.md#user-content-using-node-external-ips-as-targets

My config for the reference of others looks like this. Only the relevant parts kept. I didn't have to do anything special with the external-dns process itself.

apiVersion: apps/v1
kind: DaemonSet
spec:
  template:
    spec:
        name: nginx
        ports:
        - containerPort: 80
          hostPort: 80
          protocol: TCP
        - containerPort: 443
          hostPort: 443
          protocol: TCP

apiVersion: v1
kind: Service
metadata:
  annotations:
    external-dns.alpha.kubernetes.io/endpoints-type: NodeExternalIP
    external-dns.alpha.kubernetes.io/hostname: example.com
spec:
  type: ClusterIP
  clusterIP: None
  ports:
  - name: http
    port: 80
    protocol: TCP
    targetPort: 80
  - name: https
    port: 443
    protocol: TCP
    targetPort: 443