Using a service name results in invalid port

TykTechnologies / tyk-k8s

Kubernetes ingress controller and sidecar injector for Tyk API Gateway

https://tyk.io

Other

7 stars 5 forks source link

Using a service name results in invalid port #32

Open excieve opened 5 years ago

excieve commented 5 years ago

Using a service name instead of a port number in the ingress doesn't appear to resolve it and the API definition target ends up with port 0. Which also doesn't appear to be updated when changed in the ingress (controller doesn't detect that something's changed it seems).

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, please comment if you would like this issue to remain open. Thank you for your contributions.

excieve commented 4 years ago

This is not stale.

joshblakeley commented 4 years ago

@excieve Can you give an example ingress spec this happens for?