7:47 a.m.
We'll eventually put together a kub (and openshift) quickstart that
sets up an ingress with SSL, db, clustered keycloak, and a secured
app. Basically something you can spin up in minikube with little to
no config with further docs on how to bring it into a real
environment. A bunch of us have bits and pieces of this, but we
haven't had the time to formalize and finish it.
On Fri, Jan 19, 2018 at 8:42 AM, Simon Payne <simonpayne58(a)gmail.com> wrote:
I did manage to get KUBE_PING working in the end and appears to be
working
great.
In my opinion, this pull request should get serious review
https://github.com/jboss-dockerfiles/keycloak/pull/96 as it worked for me.
The only changes i made were in cache.cli file
also, as it extends jboss/keycloak:latest, we dont have to build keycloak to
use it.
On Fri, Jan 19, 2018 at 1:26 PM, Bill Burke <bburke(a)redhat.com> wrote:
>
> Why didn't you use KUBE_PING? Just curious. Is there one JGroups
> stack we can rally around for kubernetes? One to rule them all so
> that Keycloak just builds automatic support for it in the distro? I
> thought the value of kubernetes was supposed to be that you could make
> these kinds of protocol/network decisions upfront.
>
> On Fri, Jan 19, 2018 at 3:29 AM, Iván Perdomo <ivan(a)akvo.org> wrote:
> > Hi,
> >
> > We're running Keycloak in Kubernetes (in Google Cloud Platform) and
> > instead of KUBE_PING we're using JDBC_PING (with a hosted MySQL by
> > Google).
> >
> > Our changes are available in the following repo:
> >
> > https://github.com/akvo/akvo-keycloak
> >
> > On 01/17/2018 12:03 PM, Simon Payne wrote:
> >> Hi all,
> >>
> >> i'm trying to get keycloak clustered on google cloud using KUBE_PING.
> >>
> >> i have a starting keycloak server using docker based on the latest
> >> keycloak
> >> and using kubernetes-0.9.3
> >>
> >> however, i get the message:
> >>
> >> [org.jgroups.protocols.kubernetes.KUBE_PING] (ServerService Thread Pool
> >> --
> >> 51) namespace not set; clustering disabled
> >>
> >> i cant figure out how to add the namespace - all example are using
> >> infinispan which uses different markup to keycloak.
> >>
> >> my standalone-ha uses <protocol
type="kubernetes.KUBE_PING"/>
> >>
> >> if i add any additional attributes on this tag then keycloak fails to
> >> start
> >>
> >> any help would be appreciated.
> >>
> >>
> >> thanks
> >>
> >> Simon.
> >> _______________________________________________
> >> keycloak-user mailing list
> >> keycloak-user(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/keycloak-user
> >>
> >
> > --
> > Iván
> >
> >
> > _______________________________________________
> > keycloak-user mailing list
> > keycloak-user(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/keycloak-user
>
>
>
> --
> Bill Burke
> Red Hat
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user
--
Bill Burke
Red Hat