Marc 'risson' Schmitt
Marc 'risson' Schmitt
Agreed, and that's what we use internally. As that would be a breaking change, and as we are slowly removing Redis as a dependency, we probably won't make the switch.
Also, since this issue has been addressed, I'm gonna go ahead and close it.
Thank you for pointing this out to us. We'll look into next steps, but I don't see any good solution yet.
So the current plan is to provide our own postgres and redis deployments, but recommend that something else is used for production deployments. Hopefully we can do this with minimal...
Target date is currently the 20th, but that might move further along if we find issues with the release.
In any case, I'd recommend you move to a postgres deployment that you manage
> Another idea: Would it make sense to persist the current sessions within Postgresql? This is already the case since 2025.4. With 2025.8, tasks will also be handled by the...
So, change of plans. For 2025.8, we'll update our default values to use the docker.io/library/postgres:17 image, with extra compatibility values so that the upgrade is seamless. For Redis, we'll probably...
Read above, we're planning to remove redis for 2025.10, so we won't be spending time on this. You can deploy valley instead of redis yourself if you want to.
Starting from 2025.10, you can disable redis in the chart. We'll remove it completely from the chart for 2025.12