-
Notifications
You must be signed in to change notification settings - Fork 326
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.
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
Support ExternalName type service sync to consul #201
Comments
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! |
Hey! Than you for the response :) |
@adilyse Does my answer satisfies your question ?:) |
Thanks Povilas, that makes sense. We'll put this request on our backlog. |
|
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. |
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. knative don't use ingress, it exposes a global service on a nodePort, and then do the redirect/reverse-proxy itself |
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
The text was updated successfully, but these errors were encountered: