Closed hguerrero closed 3 years ago
Since we separate Keycloak Frontend URL from Backend URL (see microcks/microcks#119) we not have modified the behavior of the async-minion
component. It is still requests Microcks /keycloak/config
endpoint to retrieve Keycloak Public URL. On some setups (Kind clusters or clusters using NodePort exposition) this URL may not be resolvable from outside. So we need to propagate this separation to async-minion
component first.
Fix microcks/microcks#331 then update the Operator
Now fixed with quay.io/microcks/microcks-ansible-operator:latest
container image containing the fix.
@lbroudoux Do you have a snippet of the CR config for this new option?
When deploying keycloak with privateURL in the MicrocksInstall CR, the Async minion deployment stills try to use the public url (not accessible) to connect.