I’m trying to replace an old bare metal Keycloak instance with a new one using the keycloak-operator on Kubernetes. Everything works fine, but I could not find any sign that
ssoSessionMaxLifespan are configurable through the Operator.
According to the Operator source code (where there is no reference to either of these attributes) and the structure of a sample realm-export.json file, the logical place for these attributes is at
spec.realm.ssoSessionMaxLifespan in the Keycloakrealm CRD, but this is not the case.
Are these options not configurable through the Operator CRDs, and the API is the only way to automate setting them, or am I looking at the wrong place?