Support ExternalName type service sync to consul

[povils]

Hi everyone!
Thanks for the tool, it's awesome!
Is there a reason why consul-k8s doesnt support ExternalName type service sync to Consul?
https://www.consul.io/docs/platform/k8s/service-sync.html#kubernetes-service-types

[adilyse]

Hello! Could you tell us a bit more about your use case for registering external name services? We've generally assumed that if folks are using services external to Kubernetes that they'd register them directly with Consul, so we'd like to hear more about your situation. Thanks!

[povils]

Hey! Than you for the response :)
Our use case is very simple: we want to sync ingress routes to consul. Basically what we want is to have a kubernetes resource (service, ingress routes, configmap?) inside application's chart that after the chart installation we would have automatically registered application in consul which points to ingress controller balancer. That's why I thought service with type externalname was a logical way to do it because consul-k8s already deals with kubermetes services.

[povils]

@adilyse Does my answer satisfies your question ?:)

[lkysow]

Thanks Povilas, that makes sense. We'll put this request on our backlog.

[lkysow]

To Do: Can we register services in Consul with a DNS name? I think we might need an IP. Edit: yes we just set the DNS address in the Address field. If users are leveraging Consul DNS then they need to set up DNS recursers to actually resolve that address (https://www.consul.io/docs/agent/options.html#_recursor).

[Lysholm]

Another 👍 for this.

I want to be able to register external services only one place. For connect i currently have to register services in a manifest (a terminating gateway) and "directly with consul" through terraform. If i could just create manifest files instead that would be a lot easier.

[david-yu]

Hi @povils It looks like this is a dupe of #5, would you agree? If so, I can close this and you could upvote that issue!

[VictorBac]

Hi @david-yu, that's not the same thing because not all service will have an ingress.

For example we are using knative, and it generates services of type ExternalName.
And I need those services to be registered automatically !

knative don't use ingress, it exposes a global service on a nodePort, and then do the redirect/reverse-proxy itself