Is the keycloak operator still maintained?

1

I am trying to use the keycloak operator to create a new HA Keycloak Cluster.

I have tried to create a new keycloak cluster using the yaml below from OperatorHub.io | The registry for Kubernetes Operators

apiVersion: k8s.keycloak.org/v2alpha1
kind: Keycloak
metadata:
  name: example-keycloak
  labels:
    app: sso
spec:
  instances: 1
  hostname: example.org
  tlsSecret: my-tls-secret

But I get the error

Error from server (BadRequest): error when creating "keycloak.yaml": Keycloak in version "v2alpha1" cannot be handled as a Keycloak: strict decoding error: unknown field "spec.tlsSecret"

Also the Link to Documentation on that page gives a 404 error. Leading me to think the operator may no longer be maintained.

I am new to using Operators and OLM so this kind of hassle is frustrating, but I did managed to get Postgres up running simply enough using an operator. Could some give me an example of a yaml file that will generate a cluster using OLM.

1 Like
2

Hi, did you find any fix for this problem?

3

Hey there, I noticed this issue and submitted a github issue and pull request to resolve the problem, which basically is a missing key in the example. It should look like this:

apiVersion: k8s.keycloak.org/v2alpha1
kind: Keycloak
metadata:
  name: example-keycloak
  labels:
    app: sso
spec:
  instances: 1
  hostname: example.org
  http:
    tlsSecret: my-tls-secret

Note the addition of the http: key, and indent of tlsSecret

hope that helps!

1 Like
4

Whoops, I just realized the hostname stanza is also incorrect in the upstream example. I can’t seem to update my original answer so: the actual correct structure is:

kind: Keycloak
apiVersion: k8s.keycloak.org/v2alpha1
metadata:
  name: example-keycloak
  labels:
    app: sso
  namespace: keycloak
spec:
  instances: 1
  hostname: 
    hostname: example.org
  http:
    tlsSecret: my-tls-secret