Keycloak integration with community edition

[jeremyjpj0916]

@Prashant_Shandilya I have only worked with Kong as an API Gateway in cloud architecture deployed and configured in a dockerfile. As for native k8s deployment I am not sure how Kong is configured for 3rd party plugins. Obviously their YAML configurations mentions where standard plugins live but I suppose to actually leverage 3rd party plugins you could make a custom image with the plugin put into it and then add the plugin conf to the yaml configuration. See here for some discussion on it:

Apply custom plugin via KongIngress

Custom plugins can be added to the ingress controller via volume mounts and environment variable configuration. Note that these need to be added to both the kong Deployment and the ingress-kong Deployment, as the ingress controller uses a split deployment with separate Kong nodes for the admin API and proxy. You’ll need to first create a configMap to hold your plugin source with something like kubectl create configmap custom-plugins --from-file=/path/to/kong-plugin-hello/ --namespace kong . Af…