We are trying to implement a REDIS cache (Lucee provided extension) for session management, now that we're using Kubernetes / docker containers. After changing our session management to CFML from J2EE. (no other changes were made: and perhaps that's the issue? - we're missing a change(s) that was additionally required) I find that I can no longer log into my app - and the error message I see is along the lines of the "session has expired". Just thought I would ask out aloud; "Does anyone have any ideas on how I might resolve the issue?" As I have zero Redis experience, zero Kubernetes experience and "limited" Docker experience... (An entirely different department runs the Kubernetes clusters and they are trying to help - but have zero CFML knowledge.) So hopefully there is just something obvious (to others) stuff I have missed. As always thanks.

Without the code for your "login" logic and an understanding of how your app infrastructure is set up, all anyone can offer you is conjecture. My first suggestion is look at how the Session logic is handled and does it work if you run it locally on dev. Start by mitigating the code change and then work to the infrastructure side.

@gavinbaumanis My assumption is you are using Lucee in the containers. In my applications I have the following variables set: sessionManagement = true sessionTimeout =TimeSpan setClientCookies = false sessionStorage ="cacheName" sessionCluster = true setClientCookies = false If you can connect to the container running Lucee to perform the following. 1. I would verify the container can ping the redis IP or name and port. We run a cluster of redis servers so in my case I would verify I can ping all the IPs. 2. You could also create a test CFC/CFML script to run which uses cachePut and cacheIdExists to verify you can write to redis and read the data back. I hope this helps you narrow the problem down.

Thanks @tony I will give it a go when I am back at work and let everyone know the results.