TykTechnologies / tyk-k8s

Kubernetes ingress controller and sidecar injector for Tyk API Gateway
https://tyk.io
Other
7 stars 5 forks source link

Changes in ingress path are not applied #23

Closed excieve closed 4 years ago

excieve commented 5 years ago

When changing a path (itself or e.g. a path's backend) ingress controller doesn't react. This leaves APIs in a potentially broken state. E.g. an underlying service has changed a port or the service itself is different now (with a respective change in the ingress) — requests will not reach the target anymore.

Same effect with changing a path from empty to /, which actually has implications on the api def (empty means the listen path will use an ID).

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.