Sébastien OUDRY

Hi @chrissnell ! We also use Kong 3.9 with a fork of revomatic/kong-oidc. Did you succeed installation?

Might work with our fork https://github.com/QuickSign/kong-oidc. And by setting `redirect_uri` with an unexisting path (previously, we used `https://my-app.company.com/*`). For example: ``` apiVersion: configuration.konghq.com/v1 kind: KongClusterPlugin metadata: name: oidc-company-sso-my-app annotations: kubernetes.io/ingress.class:...

> > And by setting `redirect_uri` with an unexisting path (previously, we used `https://my-app.company.com/*`). > > Setting this to a non-existing path just sends the client to the main page...

Hi! Also interrested in the reason of re-creating a valkey image. The code for this new image can be this one: https://github.com/hyperspike/valkey-operator/blob/main/Dockerfile.valkey So I believe, it's only for certificate support?