-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Are there plans to support the service type ExternalName in Kubernetes? #1142
Comments
If you decide it is something that Traefik should support I would be willing to open the PR. Good excuse for me to finally touch some Go. Took a quick look at the code and it looks like it will basically just require adding an if block here. |
@regner If you are willing to open a PR, we can definitely assist. |
Should we also add support for |
@errm The externalIp service type is for giving a kube service an external IP. I don't see a need to support that as it is just another way to access the service and traefik should be able to do that regardless as it looks at the service endpoints. |
@regner right, I misread the documentation when looking up |
All good. :) |
What version of Traefik are you using (
traefik version
)?traefik:v1.1.2
What is your environment & configuration (arguments, toml...)?
Kubernetes
What did you do?
Point an ingress at a backend service that has a type of ExternalName.
What did you expect to see?
My hope was that Traefik would route requests to the external name
What did you see instead?
These errors:
The errors make sense as I assume Traefik has no understanding that the ExternalName service type is a thing not hosted in the Kube cluster. Mostly just curious if this is something Traefik might potentially support in the future or if it is considered out side the scope of what Traefik is for.
The text was updated successfully, but these errors were encountered: