Wander Boessenkool werkt sinds 2017 voor HCS Company, waar hij klanten helpt met containerisatie en automatiserings vraagstukken. Met een focus op zowel OpenShift als Ansible automatiseert hij zowel installatie als (dagelijks) beheer van OpenShift clusters bij klanten. Hij werkt met, en schrijft over, OpenShift sinds de eerste release in 2011. Hij heeft nog steeds nachtmerries van gears en cartridges.
Adding Custom Extensions To The New (Quarkus) Keycloak Operator
In recent times the Keycloak Operator for OpenShift has moved from the old EAP based implementation to a new implementation based on Quarkus. At the same time the Custom Resource Definition for a Keycloak object has moved from apiVersion v1alpha1 to v2alpha1.
While on average this is a good move, and it brings many improvements, some functionality appears to have not made the transition yet, most notably the ability to easily add custom extensions and providers.
Since one of our customers encountered this and asked for our help we went and sought a solution to this, without having to resort to building custom images, as those would add an extra maintenance burden on an already busy team.