keycloak service doesn't get deployed with minikube/kubernetes

fabric8io / gofabric8

CLI used when working with fabric8 running on Kubernetes or OpenShift

https://fabric8.io/

Apache License 2.0

147 stars 72 forks source link

keycloak service doesn't get deployed with minikube/kubernetes #562

Closed chmouel closed 7 years ago

chmouel commented 7 years ago

Deploying gofabric8 with minikube, it waits forever after deploying :

after putting some debug, it's wating on keycloak service to come up but this doesn't seem to be configured on the kubernetes template i.e in :

https://repo1.maven.org/maven2/io/fabric8/platform/packages/fabric8-platform/2.4.24/fabric8-platform-2.4.24-kubernetes.yml

jstrachan commented 7 years ago

what CLI did you type? The fabric8-platform YAML is for 3.x of fabric8 - before KeyCloak - we use fabric8-system now

chmouel commented 7 years ago

I was using the template directly, since by default this what I get back when deploying :

http://sprunge.us/BGXe

jstrachan commented 7 years ago

yeah - looks like gofabric8 start is broken right now; wonder if we need to ensure that legacy: true is defaulted.

I'm hoping we can switch gofabric8 over to use the new system packaging ASAP; just trying to get the E2E testing going so we can be sure it works on each release