Cristian Chiru

This is very interesting and imho very useful. @ajanikow, could you please take a look?

Why not use 1 namespace for the operator with multiple arangodb clusters? One benefit of deploying each operator in its own namespace would be having different operator versions in the...

Just clear the cache and should work, not sure what is the reason for this, as I have seen it too.

https://github.com/revomatico/kong-oidc for examples

I am not sure the python method you used handles session cookies like a browser. The session cookie name is `oidc_session` by default, can be changed by setting Kong runtime...

I think this might be specific to your env. I cannot reproduce. Can you please try it on a different/fresh env? Do some cleanup of previously built images? docker prune?...

This final redirect (to the originally requested resource) is the callback URL you define in our OIDC client. It is automatic, as specified by the protocol, and for us it...

Prepared a simple test in [tree/master/test/docker-compose](../tree/master/test/docker-compose). It works fine for me. Looking closely, indeed, at the first attempt, the kong container fails with the message you reported. That is because...

Never used zlib, since we do not use cookie. However, taking a closer look at the [lua-resty-session docs](https://github.com/bungle/lua-resty-session#pluggable-compressors), there were a couple of missing dependencies for zlib. Added them to...

thank you @hanlaur for taking a serious look at this. So it should be safe to unpollute an already hacked Dockerfile with those dependencies.