You say you haven't had to dig into the internals at all, but has having a "big pile of java" even containerized, affected your operations significantly?
I've run it inside a container and not experienced tremendous issues with RAM or CPU usage, but this is for very few auth calls per day.
Also, I needed to apply some not-obvious environment / config changes to make it work behind HTTPS and inside a container without /dev/random being remounted.
Yeah, no issues here either in containers. We did have to make some custom tooling at the time to get all configuration files under source control though
Not really. But we also haven't had any issues that required taking a closer look. We're used to hosting JVM stuff since our devs produce a lot of scala code.
I'm looking forward to them switching to Quarkus, which will make it more ameneable to be run in containers.
It looks like Keycloak.X is going to be a slightly smaller pile of java :)
https://www.keycloak.org/2019/10/keycloak-x.html
You say you haven't had to dig into the internals at all, but has having a "big pile of java" even containerized, affected your operations significantly?