The new domain and the funneling of traffic to it has made toolsbeta's Kubernetes no longer functional. It redirects to <tool>.toolforge.org, which won't really do the thing.
We should fix this because it was pretty nice to have a test environment previously.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Resolved | aborrero | T125589 Allow each tool to have its own subdomain for browser sandbox/cookie isolation | |||
| Resolved | aborrero | T234617 Toolforge. introduce new domain toolforge.org | |||
| Stalled | LucasWerkmeister | T320140 Migrate wd-shex-infer from Toolforge GridEngine to Toolforge Kubernetes | |||
| Stalled | matmarex | T319707 Migrate dtcheck from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | None | T320062 Migrate steve-adder from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | None | T320011 Migrate rfa-voting-history from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | dcaro | T194332 [Epic] Make Toolforge a proper platform as a service with push-to-deploy and build packs | |||
| Open | None | T257386 Fix the proxy behavior for Kubernetes on toolsbeta |
What should the root domain be for toolsbeta? A few possibilities:
I put both "beta" and "toolsbeta" on the deny list for tool names back in November so that they would be ok to use in this manner.
It should probably be beta.toolforge.org as it's Toolforge and the 'tools' bit isn't really needed anymore as it was only there to match tools.wmflabs.org
I was looking into what it would take to fix this, but at least locally setting a Host header seems to work fine:
legoktm@toolsbeta-proxy-1:~$ curl -H "Host: test.toolforge.org" localhost Hello World, from Toolsbeta!
At least this addresses my usecase of being able to access tools locally. Is there any functionality that this is missing? If so I can take a stab at fixing it properly.
Oh! That's good to hear. It was set up so that it was possible to hit with a straight curl to the address from toolsbeta-sgebastion-04. That's almost certainly not going to work now, but this does unblock you, actually.