Not yet. We only have the docker container[1]. The main bits you get now are related to having a better runtime for running in constrained environments.
If you look at how you enable clustering, for instance:
"--cluster-stack=kubernetes","-Djgroups.dns.query=keycloak-jgroups-ping.keycloak.svc.cluster.local"
You might notice that you have only a few settings with no changes to the server configuration. That is due to the fact that we rely on the default JGroups stacks from Infinispan.
The same goes for enabling a reverse proxy using the `proxy-mode` [2] setting, where the server is pre-built with the most common settings for configuring the server to run behind a reverse proxy.
But yeah, the operator is an important enabler for running on k8s. In terms of capabilities, you should expect the same as for the wildfly distribution, I think. But in terms of runtime and running in a constrained environment, keycloak.x should help you to save some resources/cost.