The idea of keycloak init job is to wait for keycloak pods to come up, and then run to initialize the backend user in the FederatedNode realm. Without it, the api can't authenticate itself on KC.
There is a try and wait mechanism, but is not retrying efficiently causing many init pods to be spawned, giving the wrong idea that something is terribly wrong. It can also reach the max retries on fail for the job, which will not create more pods at that point.
The idea of keycloak init job is to wait for keycloak pods to come up, and then run to initialize the backend user in the
FederatedNoderealm. Without it, the api can't authenticate itself on KC. There is a try and wait mechanism, but is not retrying efficiently causing many init pods to be spawned, giving the wrong idea that something is terribly wrong. It can also reach the max retries on fail for the job, which will not create more pods at that point.