Hi all 👋 Testing out Kratos w/the Helm Charts. Creating a flow via

GET /self-service/login/browser

redirects me to

/self-service/login/flows?flow={id}

which gives me 404 although the flow ID is present in the database. If I try changing the URL to

flows?id={id}

I get what I want (in JSON). The documentation (link) indicates that it should be

flows?id={id}

as well (see the "Play-by-play" section under the screenshot).

hi there, maybe something on the ingress level config?

Hi 👋 I'm just using the Helm chart as-is, with 1 yaml file with the configurations such as secret, DSN for Postgres and redirect urls etc.

interesting, can’t say if that is a result of some wrong mapping by the chart, or maybe just a typo in the docs?

Isn't the query params for the URI's defined in the application level e.g. the source code? I would expect the Helm charts to define stuff at a higher level than that, e.g. where to map requests. And the first part of the url to be defined by me with the configuration 🤔 I'm not really able to solve it in any way since I can't control what query params get set on the 303 redirect to

login/flows

. Could perhaps do some conditional routing with k8s but that's the wrong way to attack it.

Hi @blue-caravan-99316 What are your UI urls set to? https://github.com/ory/kratos/blob/master/contrib/quickstart/kratos/cloud/kratos.yml#L45

ah, this should be your UI, not kratos.

Ah, then it makes perfect sense! I'll try to see where I got the config value I pasted above here from, I have a feeling I got it from one or your Github repos/docs. If so, I'll create a PR for it right away 👍

You probably got it from the docker-compose examples 🙂 The problem there is that both urls probably use localhost, and in a k8s scenario you have to use internal/external addresses 😄