Currently adding/removing defaultClientScopes and optionalClientScopes on the Kubernets client spec has no effect, since the ClientController only manipulates the default/optionalClientScopes lists on the ClientRepresentation and then updates the Keycloak client resource instead of using the dedicated [add|remove][Default|Optional]ClientScope operations of the Keycloak client resource. Same applies for the removal of clientScopes.
Currently adding/removing defaultClientScopes and optionalClientScopes on the Kubernets client spec has no effect, since the ClientController only manipulates the default/optionalClientScopes lists on the ClientRepresentation and then updates the Keycloak client resource instead of using the dedicated
[add|remove][Default|Optional]ClientScope
operations of the Keycloak client resource. Same applies for the removal of clientScopes.