I have created my paths like this.
https://api.syn-platform.com/service1/
https://api.syn-platform.com/service2/
Now these service1 and service2 are two independent node js backend server.
If tomorrow, If I want to change the path, from /service1 to /service1-beta/
I have to change urls and coding inside the service.
Also, I need to register my urls like /service1/health inside the codebase. I wish if ALB Ingress do some remove some portion of path so that my service will receive it as /health and not /service1/health.
fastify support Route prefixing which we are using it - https://github.com/fastify/fastify/blob/master/docs/Routes.md#route-prefixing but I wish if something can be done so that we don't need to use Route prefix too.
Hi, this is known as pathRewrite. ALB itself doesn't support this feature yet, so it's not possible for now.
But i'm aware that ALB team is building features like this
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Really hoping that the ALB team can realise such pathRewrite functionality! We now also have to rely on services implementing a URL prefix for path-based routing. We could also use NGINX as ingress controller but would rather have rewriting functionality out of the box for ALB.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
I'm also looking for this, any news?
Most helpful comment
I'm also looking for this, any news?